net.ihe.gazelle.assets.SearchCriteria : 149 assertions found for this search Review filtered assertions

Assertion

Applies to

Applied to
Not applied to

Coverage

Covered by
Not covered by
Id scheme
Assertion id
Status
Testable?
#Coverage
#Applies to
Comment
Predicate
Page
Tags
Last changed
Actions
CH-HPDCH-HPD-001reviewedTestable 0 4 the Actor must implement the CH:PIDD request validating PIDD.xsd (see Section 1.11.3.1 Provider Information Directory)58Section 1.11.36/6/19 3:05:09 PM by wbars
CH-HPDCH-HPD-002reviewedTestable 0 3 the Actor must implement the CH:PIDD response validating PIDD.xsd (see Section 1.11.3.2 Provider Information Consumer) 58Section 1.11.38/26/19 5:25:26 PM by mbesnier
CH-HPDCH-HPD-004reviewedTestable 3 1 For "Organization" the parameter "Org Type" (businessCategory) is required (see Table 16: HPD Organizational Provider Attributes) 64Section 1.11.5.1.27/1/19 2:49:06 PM by wbars
CH-HPDCH-HPD-007reviewedTestable 2 1 The ID consists of the OID for GS1 GLN plus the GLN 7 of the Provider Identifiers as a suffix number (Table 15: HPD Individual Provider Attributes) 61Section 1.11.5.1.27/1/19 2:49:06 PM by wbars
CH-HPDCH-HPD-009reviewedTestable 3 1 The parameter Provider Last Name MUST be Single-valued (see Table 15: HPD Individual Attributes)62Section 1.11.5.1.27/1/19 2:49:06 PM by wbars
CH-HPDCH-HPD-012to be reviewedTestable 3 1 For the Owing organization, the owner attribute is singled-valued and required (see Table 17: HPD Relationship Attributes)66Section 1.11.5.1.27/1/19 2:49:06 PM by wbars
CH-HPDCH-HPD-013reviewedTestable 3 1 At least, one value for hcIdentifier must start with "RefData:OID" (See Table 16: HPD Organizational Provider Attributes)64Section 1.11.5.1.27/1/19 2:49:06 PM by wbars
CH-HPDCH-HPD-014reviewedTestable 2 1 HCProfessional shall have a Format = IssuingAuthority:Code System:Code (where IssuingAuthority = BAG, CodeSystem = ID of the value set and Code = code of the respective concept) (see Table 15: HPD Individual Provider Attributes)61Section 1.11.5.1.27/1/19 2:49:06 PM by wbars
CH-HPDCH-HPD-015to be reviewedTestable 2 1 For "Organization" the parameter "Organization known names" is required (see Table 16: HPD Organization Provider Attributes)64Section 1.11.5.1.27/1/19 2:49:06 PM by wbars
CH-HPDCH-HPD-016to be reviewedTestable 2 1 For the uid, the parameter "Unique Entity Identifier" is required (see table 16: HPD Organizational Provider Attributed) 63Section 1.11.5.1.27/1/19 2:49:06 PM by wbars
CH-HPDCH-HPD-017to be reviewedTestable 2 1 For the hcIdentifier, the parameter "Org Identifiers" is required (see Table 16: HPD Organizational Provider Attributes)64Section 1.11.5.1.27/1/19 2:49:06 PM by wbars
CH-HPDCH-HPD-018to be reviewedTestable 2 1 For the HcRegisteredName, the parameter "Organization Name" is required (see Table 16: HPD Organizational Provider Attributes) 64Section 1.11.5.1.27/1/19 2:49:06 PM by wbars
IHEHPDIHEHPD-021reviewedTestable 1 0 Valid values for credentialStatus attribute are Active, Inactive, Revoked and Suspended (see Table 3.58.4.1.2.3-1: Status Code Category Values)66Section 3.58.4.1.2.38/26/19 5:25:26 PM by mbesnier
IHEHPDIHEHPD-022reviewedTestable 1 0 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)48Section 3.58.4.1.2.2.28/26/19 5:25:26 PM by mbesnier
IHEHPDIHEHPD-023reviewedTestable 1 0 Valid values for HcIdentifier Statusare attribute are Active, Inactive, Revoked and Suspended ( see Table 3.58.4.1.2.3-1: Status Code Category Values)66Section 3.58.4.1.2.38/26/19 5:25:26 PM by mbesnier
IHEHPDIHEHPD-024reviewedTestable 1 0 LDAP Syntax to be used for userSMIMECertificate attribute SHALL be Binary (see Table 3.58.4.1.2.2.2-1: Individual Provider Mapping)52Section 3.58.4.1.2.2.28/26/19 5:25:26 PM by mbesnier
IHEHPDIHEHPD-025reviewedTestable 1 0 LDAP Syntax to be used for hcSigningCertificate attribute SHALL be Binary (see Table 3.58.4.1.2.2.2-1: Individual Provider Mapping)52Section 3.58.4.1.2.2.28/26/19 5:25:26 PM by mbesnier
IHEHPDIHEHPD-026reviewedTestable 1 0 LDAP Syntax to be used for userCertificate attribute SHALL be Binary (see Table 3.58.4.1.2.2.2-1: Individual Provider Mapping)52Section 3.58.4.1.2.2.28/26/19 5:25:26 PM by mbesnier
IHEHPDIHEHPD-027reviewedTestable 1 0 LDAP Syntax to be used for HcSigningCertificate attribute SHALL be Binary (see Table 3.58.4.1.2.2.3-1: Organizational Provider Mapping)58Section 3.58.4.1.2.2.28/26/19 5:25:26 PM by mbesnier
IHEHPDIHEHPD-028reviewedTestable 1 0 telephoneNumber attribute SHALL be representing using the E.123 notation. (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) 53Section 3.58.4.1.2.2.28/26/19 5:25:26 PM by mbesnier