Transaction instance details (#114911)

Metadata

Timestamp: 6/2/23 2:36:01 PM (CEST GMT+0200)

Simulated actor: Provider Information Source

Domain: Elektronische Patient Dossier

Transaction: ITI-59

Initiator: Gazelle HPDSimulator (Provider Information Source)

Responder: Gazelle HPD Directory (Provider Information Directory)

Company's keyword: IHE)

<?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">  
  <ns2:addRequest dn="uid=hpdtest:O2,ou=HCRegulatedOrganization,dc=HPD,o=chili,c=de" requestID="2627"> 
    <ns2:attr name="businessCategory"> 
      <ns2:value>BAG:2.16.840.1.113883.6.96:22232009</ns2:value> 
    </ns2:attr>  
    <ns2:attr name="HcIdentifier"> 
      <ns2:value>2.51.1.3.76:010038:99986:Active</ns2:value> 
    </ns2:attr>  
    <ns2:attr name="hpdOrgId"> 
      <ns2:value>h!p+dt-est:O|+2</ns2:value> 
    </ns2:attr>  
    <ns2:attr name="o"> 
      <ns2:value>chili</ns2:value> 
    </ns2:attr>  
    <ns2:attr name="objectClass"> 
      <ns2:value>HCRegulatedOrganization</ns2:value>  
      <ns2:value>organization</ns2:value>  
      <ns2:value>top</ns2:value>  
      <ns2:value>HPDProvider</ns2:value> 
    </ns2:attr>  
    <ns2:attr name="HcRegisteredName"> 
      <ns2:value>Kereval</ns2:value> 
    </ns2:attr>  
    <ns2:attr name="HcSpecialisation"> 
      <ns2:value>BAG:2.16.840.1.113883.6.96:408465003</ns2:value> 
    </ns2:attr> 
  </ns2:addRequest> 
</ns2:batchRequest>
BatchRequest
Add request
requestID 2627
DN uid=hpdtest:O2,ou=HCRegulatedOrganization,dc=HPD,o=chili,c=de

Attributes

name value(s)
businessCategory
  • BAG:2.16.840.1.113883.6.96:22232009
HcIdentifier
  • 2.51.1.3.76:010038:99986:Active
hpdOrgId
  • h!p+dt-est:O|+2
o
  • chili
objectClass
  • HCRegulatedOrganization
  • organization
  • top
  • HPDProvider
HcRegisteredName
  • Kereval
HcSpecialisation
  • BAG:2.16.840.1.113883.6.96:408465003

Validation result (Status: FAILED)

$type Validation Report

Validation Report

General Information
Validation Date
2023, 06 30 - 01:06:38
Validation Service
Validation Test Status
FAILED

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 ECHOUE

Résumé des vérifications
2
18
Test
ch_hpd_013_IdentifierSyntax E - 1
Contexte
/batchRequest/addRequest[0]
Description
At least one value for hcidentifier must start with RefData:OID: .[ Assertion... ]
Test
constraint_hpd_addRequestHCRegulatedOrganization_uidRequired E - 2
Contexte
/batchRequest/addRequest[0]
Description
When the addRequest describes an Organizational Provider, the uid attribute is required (see 3.59.1 and Table 3.58.4.1.2.2.3-1: Organizational Provider Mapping)[ Assertion... ]
Test
constraint_hpd_common_HcIdentifierValue R - 1
Contexte
/batchRequest/addRequest[0]/attr[1]
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 - 2
Contexte
/batchRequest/addRequest[0]/attr[1]
Description
HcIdentifier Status SHALL be from Status Code Category Values ( see Table 3.58.4.1.2.3-1)[ Assertion... ]
Test
constraint_hpd_common_objectClassValue R - 3
Contexte
/batchRequest/addRequest[0]/attr[4]
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 - 4
Contexte
/batchRequest/addRequest[0]/attr[4]
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_HcSpecialisationSyntax R - 5
Contexte
/batchRequest/addRequest[0]/attr[6]
Description
HcSpecialisation attribute SHALL be formatted as follows : Issuing Authority:Code System:Code:CodeDisplayName (see Table 3.58.4.1.2.2.2-1: Individual Provider Mapping and Table 3.58.4.1.2.2.3-1: Organizational Provider Mapping)[ Assertion... ]
Test
ch_hpd_016_uid_format R - 6
Contexte
/batchRequest/addRequest[0]
Description
The uid SHALL only contain one colon (:). Only the following characters are allowed in the DN without escaping: Alphanumeric, Minus “-“, Colon “:”, Exclamation mark “!” and Pipe symbol “|”.
Test
ch_hpd_004_Type R - 7
Contexte
/batchRequest/addRequest[0]
Description
For HPD Organizational provider the parameter Org Type (businessCategory) is required[ Assertion... ]
Test
ch_hpd_014_Metadata_attributes R - 8
Contexte
/batchRequest/addRequest[0]
Description
Value of attributes HCRegulatedOrganization.HcSpecialisation and HCRegulatedOrganization.businessCategory must be provided in the following format : BAG:<CodeSystem>:<Code>[:<DisplayName>][ Assertion... ]
Test
ch_hpd_015_Organization_known_names R - 9
Contexte
/batchRequest/addRequest[0]
Description
For HPD Organizational provider the parameter Organization known names (O) is required[ Assertion... ]
Test
constraint_hpd_feedRequestAllowedElements R - 10
Contexte
/batchRequest
Description
A Provider Information Feed Request only supports the following elements: addRequest, delRequest, modDNRequest and modifyRequest[ Assertion... ]
Test
constraint_hpd_addRequestHCRegulaedOrganization_HcRegisteredNameRequired R - 11
Contexte
/batchRequest/addRequest[0]
Description
When the addRequest describes an Organizational Provider, the HcRegisteredName attribute is required (see 3.59.1 and Table 3.58.4.1.2.2.3-1: Organizational Provider Mapping)[ Assertion... ]
Test
constraint_hpd_addRequestHCRegulatedOrganization_HcIdentifier R - 12
Contexte
/batchRequest/addRequest[0]
Description
When the addRequest describes an Organizational Provider, the HcIdentifier attribute is required (see 3.59.1 and Table 3.58.4.1.2.2.3-1: Organizational Provider Mapping)[ Assertion... ]
Test
constraint_hpd_addRequestHCRegulatedOrganization_oRequired R - 13
Contexte
/batchRequest/addRequest[0]
Description
HCRegulatedOrganization SHALL have an o attribute (RFC 2556 section 7.5 describing Organization object class)[ Assertion... ]
Test
constraint_hpd_addRequest_createTimestampCard R - 14
Contexte
/batchRequest/addRequest[0]
Description
createTimestamp is an operation attribute that LDAP directory server maintains to capture the time when an entry was created[ Assertion... ]
Test
constraint_hpd_addRequest_dnSyntax R - 15
Contexte
/batchRequest/addRequest[0]
Description
dn attribute SHALL be formatted as a Distinguish name string.[ Assertion... ]
Test
constraint_hpd_addRequest_dnValidOu R - 16
Contexte
/batchRequest/addRequest[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... ]
Test
constraint_hpd_addRequest_modifyTimestampCard R - 17
Contexte
/batchRequest/addRequest[0]
Description
modifyTimestamp is an operation attribute that LDAP directory server maintains to capture the time when an entry was modified[ Assertion... ]
Test
constraint_hpd_addRequest_objectClassRequired R - 18
Contexte
/batchRequest/addRequest[0]
Description
objectClass attribute is required in each entry (see RFC 2256 section 7.1 top)[ 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">  
  <ns2:searchResponse requestID="2627"> 
    <ns2:searchResultDone requestID="1882"> 
      <ns2:resultCode code="0"/> 
    </ns2:searchResultDone> 
  </ns2:searchResponse> 
</ns2:batchResponse>
Batch Response
search Request
requestID 2627

Search Result Done

requestID 1882

Result code

code 0

Validation result (Status: FAILED)

$type Validation Report

Validation Report

General Information
Validation Date
2023, 06 30 - 01:06:38
Validation Service
Validation Test Status
FAILED

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 ECHOUE

Résumé des vérifications
1
2
Test
constraint_hpd_feedResponseAllowedElements E - 1
Contexte
/batchResponse
Description
A Provider Information Feed Response can only contains the following elements: addResponse, delResponse, modDNResponse, modifyResponse[ Assertion... ]
Test
constraint_hpd_ldapResult_errorMessageCard R - 1
Contexte
/batchResponse/searchResponse[0]/searchResultDone
Description
The response shall not contain any errorMessage element as any processing errors are not in scope. (see Section 3.59.4.2.2: Message Semantics)[ Assertion... ]
Test
constraint_hpd_ldapResult_resultCodeValue R - 2
Contexte
/batchResponse/searchResponse[0]/searchResultDone
Description
The resultCode for an acknowledgement shall be reported as '0' to imply acknowledgement. (see Session 3.59.4.2.2 Message Semantics)[ Assertion... ]