Transaction instance details (#114840)

Metadata

Timestamp: 10/11/22 9:32:05 AM (CEST GMT+0200)

Simulated actor: Provider Information Directory

Domain: Elektronische Patient Dossier

Transaction: ITI-59

Initiator: 84.74.60.104 (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" onError="resume" requestID="12345678987654321">  
  <ns2:addRequest dn="uid=adswiss:siatestorg,ou=HCRegulatedOrganization,dc=HPD,o=BAG,c=CH" requestID="1232112"> 
    <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>RefData:OID:2.16.756.5.30.1.221.3.3.2:active</ns2:value> 
    </ns2:attr>  
    <ns2:attr name="o"> 
      <ns2:value>AD Swiss SIA Test Organization</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="uid"> 
      <ns2:value>adswiss:siatestorg</ns2:value> 
    </ns2:attr>  
    <ns2:attr name="HcRegisteredName"> 
      <ns2:value>AD Swiss SIA Test Organization</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:addRequest>  
  <ns2:addRequest dn="uid=adswiss:rluykx,OU=HCProfessional,DC=HPD,O=BAG,C=ch" requestID="2882345676543"> 
    <ns2:attr name="cn"> 
      <ns2:value>Luykx,Roeland,adswiss:rluykx</ns2:value> 
    </ns2:attr>  
    <ns2:attr name="HcIdentifier"> 
      <ns2:value>RefData:GLN:7601003501681:active</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="objectClass"> 
      <ns2:value>HCProfessional</ns2:value>  
      <ns2:value>inetOrgPerson</ns2:value>  
      <ns2:value>HPDProvider</ns2:value>  
      <ns2:value>top</ns2:value>  
      <ns2:value>naturalPerson</ns2:value>  
      <ns2:value>person</ns2:value> 
    </ns2:attr>  
    <ns2:attr name="sn"> 
      <ns2:value>Luykx</ns2:value> 
    </ns2:attr>  
    <ns2:attr name="givenName"> 
      <ns2:value>Roeland</ns2:value> 
    </ns2:attr>  
    <ns2:attr name="displayName"> 
      <ns2:value>Roeland Luykx</ns2:value> 
    </ns2:attr>  
    <ns2:attr name="hcRegistrationStatus"> 
      <ns2:value>Unknown</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:addRequest>  
  <ns2:addRequest dn="cn=adswiss:siatestorgrluykx,ou=Relationship,dc=HPD,o=BAG,c=CH" requestID="212134567543262"> 
    <ns2:attr name="cn"> 
      <ns2:value>adswiss:siatestorgrluykx</ns2:value> 
    </ns2:attr>  
    <ns2:attr name="member"> 
      <ns2:value>uid=adswiss:rluykx,ou=HCProfessional,dc=HPD,o=BAG,c=CH</ns2:value> 
    </ns2:attr>  
    <ns2:attr name="objectClass"> 
      <ns2:value>groupOfNames</ns2:value>  
      <ns2:value>top</ns2:value> 
    </ns2:attr>  
    <ns2:attr name="owner"> 
      <ns2:value>uid=adswiss:siatestorg,ou=HCRegulatedOrganization,dc=HPD,o=BAG,c=CH</ns2:value> 
    </ns2:attr> 
  </ns2:addRequest> 
</ns2:batchRequest>
BatchRequest
requestID 12345678987654321
onError resume
Add request
requestID 1232112
DN uid=adswiss:siatestorg,ou=HCRegulatedOrganization,dc=HPD,o=BAG,c=CH

Attributes

name value(s)
businessCategory
  • BAG:2.16.840.1.113883.6.96:22232009
HcIdentifier
  • RefData:OID:2.16.756.5.30.1.221.3.3.2:active
o
  • AD Swiss SIA Test Organization
objectClass
  • HCRegulatedOrganization
  • organization
  • top
  • HPDProvider
uid
  • adswiss:siatestorg
HcRegisteredName
  • AD Swiss SIA Test Organization
hpdProviderPracticeAddress
  • streetName=Seidenstrasse$streetNumber=2$city=Wallisellen$state=ZH$postalCode=8307$country=CH$addr=Seidenstrasse 4 , 8307 Wallisellen, ZH, $status=PRIMARY
Add request
requestID 2882345676543
DN uid=adswiss:rluykx,OU=HCProfessional,DC=HPD,O=BAG,C=ch

Attributes

name value(s)
cn
  • Luykx,Roeland,adswiss:rluykx
HcIdentifier
  • RefData:GLN:7601003501681:active
HcProfession
  • BAG:2.16.756.5.30.1.127.3.10.9:00000
objectClass
  • HCProfessional
  • inetOrgPerson
  • HPDProvider
  • top
  • naturalPerson
  • person
sn
  • Luykx
givenName
  • Roeland
displayName
  • Roeland Luykx
hcRegistrationStatus
  • Unknown
gender
  • M
hpdProviderPracticeAddress
  • streetName=Seidenstrasse$streetNumber=2$city=Wallisellen$state=ZH$postalCode=8307$country=CH$addr=Seidenstrasse 4 , 8307 Wallisellen, ZH, $status=PRIMARY
Add request
requestID 212134567543262
DN cn=adswiss:siatestorgrluykx,ou=Relationship,dc=HPD,o=BAG,c=CH

Attributes

name value(s)
cn
  • adswiss:siatestorgrluykx
member
  • uid=adswiss:rluykx,ou=HCProfessional,dc=HPD,o=BAG,c=CH
objectClass
  • groupOfNames
  • top
owner
  • uid=adswiss:siatestorg,ou=HCRegulatedOrganization,dc=HPD,o=BAG,c=CH

Validation result (Status: FAILED)

$type Validation Report

Validation Report

General Information
Validation Date
2022, 10 11 - 09:33:15
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
57
Test
constraint_hpd_addRequestHCProfessional_uidRequired E - 1
Contexte
/batchRequest/addRequest[1]
Description
When the addRequest describes an Individual Provider, the uid attribute is required (see 3.59.1 and Table 3.58.4.1.2.2.2-1: Individual 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[3]
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[3]
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_uidSyntax R - 5
Contexte
/batchRequest/addRequest[0]/attr[4]
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 - 6
Contexte
/batchRequest/addRequest[0]/attr[4]
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_PostalAddressAddrMandatory R - 7
Contexte
/batchRequest/addRequest[0]/attr[6]
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 - 8
Contexte
/batchRequest/addRequest[0]/attr[6]
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 - 9
Contexte
/batchRequest/addRequest[0]/attr[6]
Description
PostalAddress syntax SHALL be dstring *( $ dstring) and enforce format of key=value[ Assertion... ]
Test
constraint_hpd_common_HcIdentifierValue R - 10
Contexte
/batchRequest/addRequest[1]/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 - 11
Contexte
/batchRequest/addRequest[1]/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 - 12
Contexte
/batchRequest/addRequest[1]/attr[3]
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 - 13
Contexte
/batchRequest/addRequest[1]/attr[3]
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_displayNameValueCard R - 14
Contexte
/batchRequest/addRequest[1]/attr[6]
Description
displayName attribute SHALL be single valued (see Table 3.58.4.1.2.2.2-1: Individual Provider Mapping)[ Assertion... ]
Test
constraint_hpd_common_genderValue R - 15
Contexte
/batchRequest/addRequest[1]/attr[8]
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 - 16
Contexte
/batchRequest/addRequest[1]/attr[8]
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 - 17
Contexte
/batchRequest/addRequest[1]/attr[9]
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 - 18
Contexte
/batchRequest/addRequest[1]/attr[9]
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 - 19
Contexte
/batchRequest/addRequest[1]/attr[9]
Description
PostalAddress syntax SHALL be dstring *( $ dstring) and enforce format of key=value[ Assertion... ]
Test
constraint_hpd_common_objectClassValue R - 20
Contexte
/batchRequest/addRequest[2]/attr[2]
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 - 21
Contexte
/batchRequest/addRequest[2]/attr[2]
Description
The objectClass attribute is present in every entry, with at least two values. (see RFC 2256 section 5.1 objectClass)[ Assertion... ]
Test
ch_hpd_004_Type R - 22
Contexte
/batchRequest/addRequest[0]
Description
For HPD Organizational provider the parameter Org Type (businessCategory) is required[ Assertion... ]
Test
ch_hpd_013_IdentifierSyntax R - 23
Contexte
/batchRequest/addRequest[0]
Description
At least one value for hcidentifier must start with RefData:OID: .[ Assertion... ]
Test
ch_hpd_014_Metadata_attributes R - 24
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 - 25
Contexte
/batchRequest/addRequest[0]
Description
For HPD Organizational provider the parameter Organization known names (O) is required[ Assertion... ]
Test
ch_hpd_009_LastName R - 26
Contexte
/batchRequest/addRequest[1]
Description
Provider Last Name (sn) MUST be Single-valued[ Assertion... ]
Test
ch_hpd_014_Metadata_attributes R - 27
Contexte
/batchRequest/addRequest[1]
Description
Value of attributes HCProfessional.HcProfession and HCProfessional.HcSpecialisation must be provided in the following format : BAG:<CodeSystem>:<Code>[:<DisplayName>][ Assertion... ]
Test
ch_hpd_012_owner R - 28
Contexte
/batchRequest/addRequest[2]
Description
When the addRequest describes a relationship, the owner attribute is required[ Assertion... ]
Test
constraint_hpd_feedRequestAllowedElements R - 29
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 - 30
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 - 31
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 - 32
Contexte
/batchRequest/addRequest[0]
Description
HCRegulatedOrganization SHALL have an o attribute (RFC 2556 section 7.5 describing Organization object class)[ Assertion... ]
Test
constraint_hpd_addRequestHCRegulatedOrganization_uidRequired R - 33
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_addRequest_createTimestampCard R - 34
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 - 35
Contexte
/batchRequest/addRequest[0]
Description
dn attribute SHALL be formatted as a Distinguish name string.[ Assertion... ]
Test
constraint_hpd_addRequest_dnValidOu R - 36
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 - 37
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 - 38
Contexte
/batchRequest/addRequest[0]
Description
objectClass attribute is required in each entry (see RFC 2256 section 7.1 top)[ Assertion... ]
Test
constraint_hpd_addRequestHCProfessional_HcIdentifierRequired R - 39
Contexte
/batchRequest/addRequest[1]
Description
When the addRequest describes an Individual Provider, the HcIdentifier attribute is required (see 3.59.1 and Table 3.58.4.1.2.2.2-1: Individual Provider Mapping)[ Assertion... ]
Test
constraint_hpd_addRequestHCProfessional_HcProfessionRequired R - 40
Contexte
/batchRequest/addRequest[1]
Description
When the addRequest describes an Individual Provider, the HcProfession attribute is required (see 3.59.1 and Table 3.58.4.1.2.2.2-1: Individual Provider Mapping)[ Assertion... ]
Test
constraint_hpd_addRequestHCProfessional_HcRegistrationStatusRequired R - 41
Contexte
/batchRequest/addRequest[1]
Description
When the addRequest describes an Individual Provider, the HcRegistrationStatus attribute is required (see ISO 21091 section 8.1.3 Healthcare Professional)[ Assertion... ]
Test
constraint_hpd_addRequestHCProfessional_cnRequired R - 42
Contexte
/batchRequest/addRequest[1]
Description
When the addRequest describes an Individual Provider, the cn attribute is required (see 3.59.1 and Table 3.58.4.1.2.2.2-1: Individual Provider Mapping)[ Assertion... ]
Test
constraint_hpd_addRequestHCProfessional_displayNameRequired R - 43
Contexte
/batchRequest/addRequest[1]
Description
When the addRequest describes an Individual Provider, the displayName attribute is required (see 3.59.1 and Table 3.58.4.1.2.2.2-1: Individual Provider Mapping)[ Assertion... ]
Test
constraint_hpd_addRequestHCProfessional_snRequired R - 44
Contexte
/batchRequest/addRequest[1]
Description
When the addRequest describes an Individual Provider, the sn attribute is required (see 3.59.1 and Table 3.58.4.1.2.2.2-1: Individual Provider Mapping)[ Assertion... ]
Test
constraint_hpd_addRequest_createTimestampCard R - 45
Contexte
/batchRequest/addRequest[1]
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 - 46
Contexte
/batchRequest/addRequest[1]
Description
dn attribute SHALL be formatted as a Distinguish name string.[ Assertion... ]
Test
constraint_hpd_addRequest_dnValidOu R - 47
Contexte
/batchRequest/addRequest[1]
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 - 48
Contexte
/batchRequest/addRequest[1]
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 - 49
Contexte
/batchRequest/addRequest[1]
Description
objectClass attribute is required in each entry (see RFC 2256 section 7.1 top)[ Assertion... ]
Test
constraint_hpd_addRequestRelationship_cnRequired R - 50
Contexte
/batchRequest/addRequest[2]
Description
When the addRequest describes a relationship, the cn attribute is required (see ISO 21021:2013, section B.4 GroupOfNames)[ Assertion... ]
Test
constraint_hpd_addRequestRelationship_groupOfNamesObjectClass R - 51
Contexte
/batchRequest/addRequest[2]
Description
Relationships in HPD are represented by LDAP objects using the groupOfNames class (see section 3.58.4.1.2.2.4 Relationships)[ Assertion... ]
Test
constraint_hpd_addRequestRelationship_ownerSV R - 52
Contexte
/batchRequest/addRequest[2]
Description
When the addRequest describes a relationship, the owner attribute is singled-valued (see section 3.58.4.1.2.2.4 Relationships)[ Assertion... ]
Test
constraint_hpd_addRequest_createTimestampCard R - 53
Contexte
/batchRequest/addRequest[2]
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 - 54
Contexte
/batchRequest/addRequest[2]
Description
dn attribute SHALL be formatted as a Distinguish name string.[ Assertion... ]
Test
constraint_hpd_addRequest_dnValidOu R - 55
Contexte
/batchRequest/addRequest[2]
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 - 56
Contexte
/batchRequest/addRequest[2]
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 - 57
Contexte
/batchRequest/addRequest[2]
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:errorResponse requestID="12345678987654321"> 
    <ns2:message>&lt;batchResponse xmlns="urn:oasis:names:tc:DSML:2:0:core" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"&gt;&lt;errorResponse xmlns="" type="malformedRequest"&gt;&lt;message&gt;ERR_03001 ERR_03039 the given requestID is not an integer (position: START_TAG seen ...MLSchema-instance" onError="resume" requestID="12345678987654321"&amp;gt;... @2:209) caused by: java.lang.NumberFormatException: For input string: "12345678987654321" - Line 2 - Column 209&lt;/message&gt;&lt;/errorResponse&gt;&lt;/batchResponse&gt;</ns2:message> 
  </ns2:errorResponse> 
</ns2:batchResponse>
Batch Response
error Response
requestID 12345678987654321

Message

<batchResponse xmlns="urn:oasis:names:tc:DSML:2:0:core" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><errorResponse xmlns="" type="malformedRequest"><message>ERR_03001 ERR_03039 the given requestID is not an integer (position: START_TAG seen ...MLSchema-instance" onError="resume" requestID="12345678987654321"&gt;... @2:209) caused by: java.lang.NumberFormatException: For input string: "12345678987654321" - Line 2 - Column 209</message></errorResponse></batchResponse>

Validation result (Status: PASSED)

$type Validation Report

Validation Report

General Information
Validation Date
2022, 10 11 - 09:33:15
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
1
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... ]