Transaction instance details (#114870)

Metadata

Timestamp: 12/7/22 12:24:35 PM (CET GMT+0100)

Simulated actor: Provider Information Directory

Domain: Elektronische Patient Dossier

Transaction: ITI-59

Initiator: 194.209.244.120 (Provider Information Source)

Responder: HPDSimulator (Provider Information Directory)

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

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

Request: CH - Provider Information Feed Request
Response: CH - Provider Information Feed Response

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" onError="exit" processing="sequential" requestID="630214612" responseOrder="sequential">
  <ns2:addRequest dn="uid=Abilis:1529124,ou=HCProfessional,dc=HPD,o=BAG,c=CH" requestID="874034702">
    <ns2:attr name="uid">
      <ns2:value>Abilis:1529124</ns2:value>
    </ns2:attr>
    <ns2:attr name="hcidentifier">
      <ns2:value>RefData:GLN:7601003330977:active</ns2:value>
    </ns2:attr>
    <ns2:attr name="sn">
      <ns2:value>GFPone</ns2:value>
    </ns2:attr>
    <ns2:attr name="givenname">
      <ns2:value>Abilis</ns2:value>
    </ns2:attr>
    <ns2:attr name="hcprofession">
      <ns2:value>BAG:2.16.840.1.113883.6.96:46255001</ns2:value>
    </ns2:attr>
    <ns2:attr name="objectclass">
      <ns2:value>top</ns2:value>
      <ns2:value>person</ns2:value>
      <ns2:value>naturalPerson</ns2:value>
      <ns2:value>inetOrgPerson</ns2:value>
      <ns2:value>organizationalPerson</ns2:value>
      <ns2:value>HPDProvider</ns2:value>
      <ns2:value>HCProfessional</ns2:value>
    </ns2:attr>
    <ns2:attr name="hcregistrationstatus">
      <ns2:value>Unknown</ns2:value>
    </ns2:attr>
    <ns2:attr name="displayname">
      <ns2:value>Abilis GFPone</ns2:value>
    </ns2:attr>
    <ns2:attr name="cn">
      <ns2:value>GFPone, Abilis, Abilis:1529124</ns2:value>
    </ns2:attr>
  </ns2:addRequest>
</ns2:batchRequest>

Message content (HTML)

BatchRequest

requestID	630214612
processing	sequential
responseOrder	sequential
onError	exit

Add request

requestID	874034702
DN	uid=Abilis:1529124,ou=HCProfessional,dc=HPD,o=BAG,c=CH

Attributes

name	value(s)
uid	Abilis:1529124
hcidentifier	RefData:GLN:7601003330977:active
sn	GFPone
givenname	Abilis
hcprofession	BAG:2.16.840.1.113883.6.96:46255001
objectclass	top person naturalPerson inetOrgPerson organizationalPerson HPDProvider HCProfessional
hcregistrationstatus	Unknown
displayname	Abilis GFPone
cn	GFPone, Abilis, Abilis:1529124

Validation result (Status: PASSED)

$type Validation Report

Validation Report

General Information

Validation Date: 2023, 03 07 - 10:24:33
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: 22

Test: constraint_hpd_common_uidSyntax R - 1
Contexte: /batchRequest/addRequest[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: /batchRequest/addRequest[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_HcIdentifierValue R - 3
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 - 4
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 - 5
Contexte: /batchRequest/addRequest[0]/attr[5]
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 - 6
Contexte: /batchRequest/addRequest[0]/attr[5]
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 - 7
Contexte: /batchRequest/addRequest[0]/attr[7]
Description: displayName attribute SHALL be single valued (see Table 3.58.4.1.2.2.2-1: Individual Provider Mapping)[ Assertion... ]

Test: ch_hpd_009_LastName R - 8
Contexte: /batchRequest/addRequest[0]
Description: Provider Last Name (sn) MUST be Single-valued[ Assertion... ]

Test: ch_hpd_014_Metadata_attributes R - 9
Contexte: /batchRequest/addRequest[0]
Description: Value of attributes HCProfessional.HcProfession and HCProfessional.HcSpecialisation must be provided in the following format : BAG:<CodeSystem>:<Code>[:<DisplayName>][ 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_addRequestHCProfessional_HcIdentifierRequired R - 11
Contexte: /batchRequest/addRequest[0]
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 - 12
Contexte: /batchRequest/addRequest[0]
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 - 13
Contexte: /batchRequest/addRequest[0]
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 - 14
Contexte: /batchRequest/addRequest[0]
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 - 15
Contexte: /batchRequest/addRequest[0]
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 - 16
Contexte: /batchRequest/addRequest[0]
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_addRequestHCProfessional_uidRequired R - 17
Contexte: /batchRequest/addRequest[0]
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_addRequest_createTimestampCard R - 18
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 - 19
Contexte: /batchRequest/addRequest[0]
Description: dn attribute SHALL be formatted as a Distinguish name string.[ Assertion... ]

Test: constraint_hpd_addRequest_dnValidOu R - 20
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 - 21
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 - 22
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" requestID="630214612">
  <ns2:addResponse requestID="4084">
    <ns2:resultCode code="0"/>
  </ns2:addResponse>
</ns2:batchResponse>

Message content (HTML)

Batch Response

requestID

630214612

add Response

requestID

4084

Result code

code

0

Validation result (Status: )

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

Back to top