HPD Simulator

Transaction instance details (#48490)

Metadata

Timestamp: 11/25/21 1:23:21 PM (CET GMT+0100)

Simulated actor: Provider Information Directory

Domain: Elektronische Patient Dossier

Transaction: ITI-59

Initiator: 127.0.0.1 (Provider Information Source)

Responder: HPDSimulator (Provider Information Directory)

Permanent link: https://ehealthsuisse.ihe-europe.net/HPDSimulator/messages/messageDisplay.seam?id=48490

Permanent link to test report: https://ehealthsuisse.ihe-europe.net/HPDSimulator/rest/GetReport?id=48490

Message content (XML)

<?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="ou=HCRegulatedOrganization,dc=HPD,o=BAG,c=CH" requestID="2829">
    <ns2:attr name="businessCategory">
      <ns2:value>required attribute</ns2:value>
    </ns2:attr>
    <ns2:attr name="HcIdentifier">
      <ns2:value>required attribute</ns2:value>
    </ns2:attr>
    <ns2:attr name="hpdOrgId">
      <ns2:value>required attribute</ns2:value>
    </ns2:attr>
    <ns2:attr name="o">
      <ns2:value>required attribute</ns2:value>
    </ns2:attr>
    <ns2:attr name="objectClass">
      <ns2:value>top</ns2:value>
      <ns2:value>HPDProvider</ns2:value>
      <ns2:value>HCRegulatedOrganization</ns2:value>
      <ns2:value>organization</ns2:value>
    </ns2:attr>
  </ns2:addRequest>
</ns2:batchRequest>

Message content (HTML)

BatchRequest

Add request

requestID	2829
DN	ou=HCRegulatedOrganization,dc=HPD,o=BAG,c=CH

Attributes

name	value(s)
businessCategory	required attribute
HcIdentifier	required attribute
hpdOrgId	required attribute
o	required attribute
objectClass	top HPDProvider HCRegulatedOrganization organization

Validation result (Status: FAILED)

$type Validation Report

Validation Report

General Information

Validation Date: 2021, 11 25 - 04:59:52
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: 5

13

Test: constraint_hpd_common_HcIdentifierValue E - 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: ch_hpd_013_IdentifierSyntax E - 2
Contexte: /batchRequest/addRequest[0]
Description: At least one value for hcidentifier must start with RefData:OID: .[ Assertion... ]

Test: ch_hpd_014_Metadata_attributes E - 3
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: constraint_hpd_addRequestHCRegulaedOrganization_HcRegisteredNameRequired E - 4
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_uidRequired E - 5
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_HcIdentifierValue2 R - 1
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 - 2
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 - 3
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: ch_hpd_004_Type R - 4
Contexte: /batchRequest/addRequest[0]
Description: For HPD Organizational provider the parameter Org Type (businessCategory) is required[ Assertion... ]

Test: ch_hpd_015_Organization_known_names R - 5
Contexte: /batchRequest/addRequest[0]
Description: For HPD Organizational provider the parameter Organization known names (O) is required[ Assertion... ]

Test: constraint_hpd_feedRequestAllowedElements R - 6
Contexte: /batchRequest
Description: A Provider Information Feed Request only supports the following elements: addRequest, delRequest, modDNRequest and modifyRequest[ Assertion... ]

Test: constraint_hpd_addRequestHCRegulatedOrganization_HcIdentifier R - 7
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 - 8
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 - 9
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 - 10
Contexte: /batchRequest/addRequest[0]
Description: dn attribute SHALL be formatted as a Distinguish name string.[ Assertion... ]

Test: constraint_hpd_addRequest_dnValidOu R - 11
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 - 12
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 - 13
Contexte: /batchRequest/addRequest[0]
Description: objectClass attribute is required in each entry (see RFC 2256 section 7.1 top)[ Assertion... ]

Message content (XML)

<?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="2829">
    <ns2:searchResultDone requestID="891">
      <ns2:resultCode code="0"/>
    </ns2:searchResultDone>
  </ns2:searchResponse>
</ns2:batchResponse>

Message content (HTML)

Batch Response

search Request

requestID

2829

Search Result Done

requestID

891

Result code

code

Validation result (Status: )

Validation of the response has not been performed yet or is not available