Transaction instance details (#114842)

Metadata

Timestamp: 10/11/22 9:35:19 AM (CEST GMT+0200)

Simulated actor: Provider Information Directory

Domain: Elektronische Patient Dossier

Transaction: ITI-58

Initiator: 84.74.60.104 (Provider Information Consumer)

Responder: HPDSimulator (Provider Information Directory)

<?xml version="1.0" encoding="UTF-8"?>

<ns2:batchRequest xmlns:ns2="urn:oasis:names:tc:DSML:2:0:core" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" requestID="677579276">  
  <ns2:searchRequest derefAliases="neverDerefAliases" dn="ou=HCProfessional,dc=HPD,o=BAG,c=CH" scope="wholeSubtree" requestID="605087439"> 
    <ns2:filter> 
      <ns2:and> 
        <ns2:substrings name="uid"> 
          <ns2:initial>adswiss:rluykx</ns2:initial> 
        </ns2:substrings>  
        <ns2:not> 
          <ns2:equalityMatch name="objectClass"> 
            <ns2:value>HCRegulatedOrganization</ns2:value> 
          </ns2:equalityMatch> 
        </ns2:not> 
      </ns2:and> 
    </ns2:filter> 
  </ns2:searchRequest> 
</ns2:batchRequest>
BatchRequest
requestID 677579276
Search request
requestID 605087439
DN ou=HCProfessional,dc=HPD,o=BAG,c=CH
Scope wholeSubtree
deref aliases neverDerefAliases

Filter

uid starts with adswiss:rluykx


Validation result (Status: PASSED)

$type Validation Report

Validation Report

General Information
Validation Date
2022, 10 11 - 09:35:42
Validation Service
Validation Test Status
PASSED

Document bien forméREUSSI

The document you have validated is supposed to be a well-formed document. The validator has checked if it is well-formed, results of this validation are gathered in this section.
The document is well-formed

Résultat de la validation avec le schemaREUSSI

Your document has been validated with the appropriate schema, here is the detail of the validation outcome.
Le document est conforme au schéma

Résultat de la validation Gazelle Objects Checker REUSSI

Résumé des vérifications
3
Test
constraint_hpd_queryRequestAllowedElements R - 1
Contexte
/batchRequest
Description
A Provider Information Query Request can only contains searchRequest elements.[ Assertion... ]
Test
constraint_hpd_searchRequest_dnSyntax R - 2
Contexte
/batchRequest/searchRequest[0]
Description
dn attribute SHALL be formatted as a Distinguish name string.[ Assertion... ]
Test
constraint_hpd_searchRequest_dnValidOu R - 3
Contexte
/batchRequest/searchRequest[0]
Description
Nodes that are subordinates to dc=HPD are ou=HCProfessional, ou=HCRegulatedOrganization, ou=HPDCredential and ou=Relationship (see section 3.58.4.1.2.1 HPD Schema Structure)[ Assertion... ]
<?xml version="1.0" encoding="UTF-8"?>

<ns2:batchResponse xmlns:ns2="urn:oasis:names:tc:DSML:2:0:core" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" requestID="677579276">  
  <ns2:searchResponse requestID="2"> 
    <ns2:searchResultEntry dn="uid=adswiss:rluykx,ou=HCProfessional,dc=HPD,o=BAG,c=CH" requestID="3811"> 
      <ns2:attr name="uid"> 
        <ns2:value>adswiss:rluykx</ns2:value> 
      </ns2:attr>  
      <ns2:attr name="sn"> 
        <ns2:value>Luykx</ns2:value> 
      </ns2:attr>  
      <ns2:attr name="hcRegistrationStatus"> 
        <ns2:value>Unknown</ns2:value> 
      </ns2:attr>  
      <ns2:attr name="cn"> 
        <ns2:value>Luykx,Roeland,adswiss:rluykx</ns2:value> 
      </ns2:attr>  
      <ns2:attr name="HcProfession"> 
        <ns2:value>BAG:2.16.756.5.30.1.127.3.10.9:00000</ns2:value> 
      </ns2:attr>  
      <ns2:attr name="givenName"> 
        <ns2:value>Roeland</ns2:value> 
      </ns2:attr>  
      <ns2:attr name="gender"> 
        <ns2:value>M</ns2:value> 
      </ns2:attr>  
      <ns2:attr name="hpdProviderPracticeAddress"> 
        <ns2:value>streetName=Seidenstrasse$streetNumber=2$city=Wallisellen$state=ZH$postalCode=8307$country=CH$addr=Seidenstrasse 4 , 8307 Wallisellen, ZH, $status=PRIMARY</ns2:value> 
      </ns2:attr>  
      <ns2:attr name="objectClass"> 
        <ns2:value>top</ns2:value>  
        <ns2:value>person</ns2:value>  
        <ns2:value>organizationalPerson</ns2:value>  
        <ns2:value>inetOrgPerson</ns2:value>  
        <ns2:value>HPDProvider</ns2:value>  
        <ns2:value>HCProfessional</ns2:value>  
        <ns2:value>naturalPerson</ns2:value> 
      </ns2:attr>  
      <ns2:attr name="HcIdentifier"> 
        <ns2:value>RefData:GLN:7601003501681:active</ns2:value> 
      </ns2:attr>  
      <ns2:attr name="displayName"> 
        <ns2:value>Roeland Luykx</ns2:value> 
      </ns2:attr> 
    </ns2:searchResultEntry>  
    <ns2:searchResultDone requestID="2"> 
      <ns2:resultCode code="0" descr="success"/> 
    </ns2:searchResultDone> 
  </ns2:searchResponse> 
</ns2:batchResponse>
Batch Response
requestID 677579276
search Request
requestID 2

Search result entry

requestID 3811
DN uid=adswiss:rluykx,ou=HCProfessional,dc=HPD,o=BAG,c=CH

Attributes

name value(s)
uid
  • adswiss:rluykx
sn
  • Luykx
hcRegistrationStatus
  • Unknown
cn
  • Luykx,Roeland,adswiss:rluykx
HcProfession
  • BAG:2.16.756.5.30.1.127.3.10.9:00000
givenName
  • Roeland
gender
  • M
hpdProviderPracticeAddress
  • streetName=Seidenstrasse$streetNumber=2$city=Wallisellen$state=ZH$postalCode=8307$country=CH$addr=Seidenstrasse 4 , 8307 Wallisellen, ZH, $status=PRIMARY
objectClass
  • top
  • person
  • organizationalPerson
  • inetOrgPerson
  • HPDProvider
  • HCProfessional
  • naturalPerson
HcIdentifier
  • RefData:GLN:7601003501681:active
displayName
  • Roeland Luykx

Search Result Done

requestID 2

Result code

code 0

Validation result (Status: PASSED)

$type Validation Report

Validation Report

General Information
Validation Date
2022, 10 11 - 09:35:42
Validation Service
Validation Test Status
PASSED

Document bien forméREUSSI

The document you have validated is supposed to be a well-formed document. The validator has checked if it is well-formed, results of this validation are gathered in this section.
The document is well-formed

Résultat de la validation avec le schemaREUSSI

Your document has been validated with the appropriate schema, here is the detail of the validation outcome.
Le document est conforme au schéma

Résultat de la validation Gazelle Objects Checker REUSSI

Résumé des vérifications
16
Test
constraint_hpd_common_uidSyntax R - 1
Contexte
/batchResponse/searchResponse[0]/searchResultEntry[0]/attr[0]
Description
uid attribute SHALL be formatted using the RDN Format as defined by ISO21091 section 9.2: IssuingAuhorityName:ID (see Tables 3.58.4.1.2.2.2-1: Individual Provider Mapping and 3.58.4.1.2.2.3-1: Organizational Provider Mapping)[ Assertion... ]
Test
constraint_hpd_common_uidValueCard R - 2
Contexte
/batchResponse/searchResponse[0]/searchResultEntry[0]/attr[0]
Description
uid attribute SHALL be single valued (see Tables 3.58.4.1.2.2.2-1: Individual Provider Mapping and 3.58.4.1.2.2.3-1: Organizational Provider Mapping)[ Assertion... ]
Test
constraint_hpd_common_genderValue R - 3
Contexte
/batchResponse/searchResponse[0]/searchResultEntry[0]/attr[6]
Description
gender attribute SHALL follow the Natural Person auxilary class as defined in RFC 2985, that means that only Male (M or m) and Female (F or f) values are allowed. (see Table 3.58.4.1.2.2.2-1)[ Assertion... ]
Test
constraint_hpd_common_genderValueCard R - 4
Contexte
/batchResponse/searchResponse[0]/searchResultEntry[0]/attr[6]
Description
gender attribute SHALL be single valued (see Table 3.58.4.1.2.2.2-1: Individual Provider Mapping)[ Assertion... ]
Test
constraint_hpd_common_PostalAddressAddrMandatory R - 5
Contexte
/batchResponse/searchResponse[0]/searchResultEntry[0]/attr[7]
Description
If an address is included, then the addr is required (see section 3.58.4.1.2.2.1 Object Classes)[ Assertion... ]
Test
constraint_hpd_common_PostalAddressStatus R - 6
Contexte
/batchResponse/searchResponse[0]/searchResultEntry[0]/attr[7]
Description
Valid values for postal address status are Primary, Secondary, Inactive (see Table 3.58.4.1.2.3-1: Status Code Category Values)[ Assertion... ]
Test
constraint_hpd_common_PostalAddressSyntax R - 7
Contexte
/batchResponse/searchResponse[0]/searchResultEntry[0]/attr[7]
Description
PostalAddress syntax SHALL be dstring *( $ dstring) and enforce format of key=value[ Assertion... ]
Test
constraint_hpd_common_objectClassValue R - 8
Contexte
/batchResponse/searchResponse[0]/searchResultEntry[0]/attr[8]
Description
objectClass attribute SHALL be present in every entry, one of the values is either top or alias (see RFC 2256 section 5.1 objectClass)[ Assertion... ]
Test
constraint_hpd_common_objectClassValueCard R - 9
Contexte
/batchResponse/searchResponse[0]/searchResultEntry[0]/attr[8]
Description
The objectClass attribute is present in every entry, with at least two values. (see RFC 2256 section 5.1 objectClass)[ Assertion... ]
Test
constraint_hpd_common_HcIdentifierValue R - 10
Contexte
/batchResponse/searchResponse[0]/searchResultEntry[0]/attr[9]
Description
HcIdentifier SHALL be formatted as defined by ISO 21091 (IssuingAuthority:Type:ID:Status) (see Tables 3.58.4.1.2.2.2-1: Individual Provider Mapping, 3.58.4.1.2.2.3-1: Organizational Provider Mapping)[ Assertion... ]
Test
constraint_hpd_common_HcIdentifierValue2 R - 11
Contexte
/batchResponse/searchResponse[0]/searchResultEntry[0]/attr[9]
Description
HcIdentifier Status SHALL be from Status Code Category Values ( see Table 3.58.4.1.2.3-1)[ Assertion... ]
Test
constraint_hpd_common_displayNameValueCard R - 12
Contexte
/batchResponse/searchResponse[0]/searchResultEntry[0]/attr[10]
Description
displayName attribute SHALL be single valued (see Table 3.58.4.1.2.2.2-1: Individual Provider Mapping)[ Assertion... ]
Test
constraint_hpd_queryResponseAllowedElements R - 13
Contexte
/batchResponse
Description
A provider information query response can only constains searchResponse elements[ Assertion... ]
Test
constraint_hpd_searchResponse_requestIDCard R - 14
Contexte
/batchResponse/searchResponse[0]
Description
The Provider Information Query Response shall contain the requestID to associate the response to the Provider Information Query Request. (see section 3.58.4.2.2: Message Semantics)[ Assertion... ]
Test
constraint_hpd_searchReponse_searchResultEntryDNSyntax R - 15
Contexte
/batchResponse/searchResponse[0]/searchResultEntry[0]
Description
dn attribute SHALL be formatted as a Distinguish name string.[ Assertion... ]
Test
constraint_hpd_searchResponse_SearchResultEntryDnValidOu R - 16
Contexte
/batchResponse/searchResponse[0]/searchResultEntry[0]
Description
Nodes that are subordinates to dc=HPD are ou=HCProfessional, ou=HCRegulatedOrganization, ou=HPDCredential and ou=Relationship (see section 3.58.4.1.2.1 HPD Schema Structure)[ Assertion... ]