Transaction instance details (#114650)

Metadata

Timestamp: 8/11/22 3:09:44 PM (CEST GMT+0200)

Simulated actor: Provider Information Directory

Domain: Elektronische Patient Dossier

Transaction: ITI-59

Initiator: 85.195.225.94 (Provider Information Source)

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="51">  
  <ns2:modifyRequest dn="uid=Abilis:7fcdb994-59ee-4851-8ae6-0252091btr5z,ou=HCRegulatedOrganization,DC=HPD,O=BAG,C=CH" requestID="35"> 
    <ns2:modification name="pager" operation="add"> 
      <ns2:value>004171154</ns2:value> 
    </ns2:modification> 
  </ns2:modifyRequest> 
</ns2:batchRequest>
BatchRequest
requestID 51
Modify request
requestID 35
DN uid=Abilis:7fcdb994-59ee-4851-8ae6-0252091btr5z,ou=HCRegulatedOrganization,DC=HPD,O=BAG,C=CH

Modifications

Modified attribute operation value(s)
pager add
  • 004171154

Validation result (Status: PASSED)

$type Validation Report

Validation Report

General Information
Validation Date
2022, 08 11 - 03:12:19
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
6
Test
constraint_hpd_feedRequestAllowedElements R - 1
Contexte
/batchRequest
Description
A Provider Information Feed Request only supports the following elements: addRequest, delRequest, modDNRequest and modifyRequest[ Assertion... ]
Test
constraint_hpd_modifyRequest_createTimestampCard R - 2
Contexte
/batchRequest/modifyRequest[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_modifyRequest_dnSyntax R - 3
Contexte
/batchRequest/modifyRequest[0]
Description
dn attribute SHALL be formatted as a Distinguish name string.[ Assertion... ]
Test
constraint_hpd_modifyRequest_dnValidOu R - 4
Contexte
/batchRequest/modifyRequest[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_modifyRequest_modifyTimestampCard R - 5
Contexte
/batchRequest/modifyRequest[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_modifyRequest_pagerSyntax R - 6
Contexte
/batchRequest/modifyRequest[0]/modification[0]
Description
pager attribute SHALL be representing using the E.123 notation. (see Tables 3.58.4.1.2.2.2-1: Individual Provider Mapping)[ 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="51">  
  <ns2:modifyResponse requestID="2"> 
    <ns2:resultCode code="0"/> 
  </ns2:modifyResponse> 
</ns2:batchResponse>
Batch Response
requestID 51
modify Response
requestID 2

Result code

code 0

Validation result (Status: PASSED)

$type Validation Report

Validation Report

General Information
Validation Date
2022, 08 11 - 03:12:22
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_feedResponseAllowedElements R - 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 - 2
Contexte
/batchResponse/modifyResponse[0]
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 - 3
Contexte
/batchResponse/modifyResponse[0]
Description
The resultCode for an acknowledgement shall be reported as '0' to imply acknowledgement. (see Session 3.59.4.2.2 Message Semantics)[ Assertion... ]