Search Criteria : 43 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-ATNACH-ATNA-005validatedTestable 7 1 In audit records generated by IHE and EPR actors, the OID of the audit source MUST be specified in AuditSourceIdentification/@AuditEnterpriseSiteID attribute8Section 1.53/18/24 7:40:01 AM by testAuto
CH-ATNACH-ATNA-007validatedTestable 7 1 For audit records generated by IHE and EPR actors, In the "AuditMessage/ParticipantObjectIdentification" node, for the value of the "@ParticipantObjectSensitivity" field, the current confidentiality code of the object MUST be specified IF KNOWN when the object is a document in the EPR. This value MUST represent a value from the Swiss Metadata Value Set, the attribute @codeSystemName (2.16.756.5.30.1.127.3.10.6). The following sequences are required OID as the code system name, e.g 1051000195109^normal^2.16.840.1.113883.6.968Section 1.53/18/24 7:39:59 AM by testAuto
CH-ATNACH-ATNA-010to be reviewedNot testable 0 1 For audit records generated by IHE and EPR actors, in all elements of the type CodedValueType: whenever the represented code belongs to the Swiss Metadata Value Set, the attribute @codeSystemName shall contain the OID of the corresponding code system instead of its symbolic name. For all other codes, this requirement is optional.8Section 1.510/1/21 3:05:11 PM by vhofman
CH-PDQCH-PDQ-001reviewedTestable 2 1 The PatientTelecom Query Parameter MUST NOT be used (see Table 12 : Message Information Model for The Patient Registry Query by Demographics Message) 39Section 1.10.2.111/25/21 2:50:08 PM by vhofman
CH-PDQCH-PDQ-006reviewedTestable 3 1 In the "Patient" parameter, the "id" field should be valued with at least one Patient Identifier (see Table 13: Message Information Model for Patient Registry Find Candidates) 42Section 1.10.3.111/25/21 2:50:08 PM by vhofman
CH-PDQCH-PDQ-007reviewedTestable 4 1 In the "Person" parameter either "Person.name" or "Patient.id" must be non-null (see Table 13: Message Information Model for Patient Regitry Find Candidates) 42Section 1.10.3.111/25/21 2:50:08 PM by vhofman
CH-PDQCH-PDQ-008reviewedTestable 4 1 In the "Person" parameter, in the "name" field the birth name is passed with the qualifier BR (see Table 10: Message Information Model for Patient Registry Find Candidatess) 33Section 1.9.2.111/25/21 2:50:08 PM by vhofman
CH-PDQCH-PDQ-009reviewedTestable 4 1 In the "Person" parameter, the "religiousAffiliationCode" MUST NOT be used (see Table 13: Message Information Model for Patient Registry Find Candidates)42Section 1.10.3.111/25/21 2:50:09 PM by vhofman
CH-PDQCH-PDQ-010reviewedTestable 4 1 In the "Person" parameter the "raceCode" field MUST NOT be used (see Table 13: Message Information Model for Patient Registry Find Candidates)42Section 1.10.3.111/25/21 2:50:09 PM by vhofman
CH-PDQCH-PDQ-011reviewedTestable 4 1 In the "Person" parameter, the "ethnicGroupCode" MUST NOT be used (see Table 9: Patient Active and Revise Model Attributes)29Section 1.7.1.111/25/21 2:50:09 PM by vhofman
CH-PDQCH-PDQ-012reviewedTestable 3 1 In the "OtherIDs" parameter, the EPR-PID MAY be added here (see Table 10: Message Information Model for Patient Registry Find Candidates)33Section 1.9.2.111/25/21 2:50:09 PM by vhofman
CH-PDQCH-PDQ-013reviewedTestable 2 1 idem pixIn the "PersonalRelationship" parameter the code MUST be "FTH" for the Father and "MTH" for the Mother (see Table 10: Message Information Model for Patient Registry Find Candidates)33Section 1.9.2.111/25/21 2:50:09 PM by vhofman
CH-PDQCH-PDQ-014reviewedTestable 1 1 If there are more than 5 matches, there must be a special handling like in the XCPD transaction (see IHE ITI TF-2b, chapter 3.55.4.2.2.6) (see Section 1.9.2.1.1 Special handling for more attributes requested) 37Section 1.9.2.1.111/25/21 2:50:09 PM by vhofman
CH-PDQCH-PDQ-015reviewedTestable 0 1 The different return cases should be handled equivalent to the XCPD cases in IHE ITI TF-2b, chapter 3.55.4.2.3 Expected Actions (see Section 1.9.2.1.1 Special handling for more attributes requested)37Section 1.9.2.1.111/25/21 2:50:09 PM by vhofman
CH-XCACH-XCA-001reviewedTestable 3 0 In Stored Queries (transaction ITI-38), the parameter $MetadataLevel, whenever provided, shall equal to 1 (one) (see Section 1.2.1 MetadataLevel).6Figure 1.21/7/22 9:38:47 AM by vhofman
CH-XCACH-XCA-002reviewedTestable 2 0 Agreed to do not cover this assertionWhenever a receiving actor (e.g. a Document Registry) discovers that this requirement ($MetadataLevel) is violated in an incoming request, it shall reject this request and return an error with the code XDSRegistryError (see section1.3) (See Section 1.2.1 MetadataLevel) 6Section 1.27/2/21 9:25:41 AM by aeschlimann
CH-XCPDCH-XCPD-001reviewedTestable 1 1 For the EPR only the Shared/National Patient Identifier Query mode MUST be used. Other modes as defined in this transaction (see also IHE ITI TF-2b, chapter 3.55.1) MUST NOT be used (see Section 1.10.1 Modes and Options)38Section 1.10.17/2/21 10:46:37 AM by aeschlimann
CH-XCPDCH-XCPD-002reviewedTestable 0 1 The Health Data Locator and Revoke Option of the Patient Location Query transaction [ITI-56] MUST NOT be used (see Section 1.10.1 Modes and Options)38Section 1.10.17/2/21 10:46:37 AM by aeschlimann
CH-XCPDCH-XCPD-003reviewedTestable 0 1 The Initiating Gateway may specify a duration value in the SOAP Header element of the request. This value suggests to the Responding Gateway a length of time that the Initiating Gateway recommends caching any correlation resulting from the interaction. This values MUST NOT exceed 3 days. See also IHE ITI TF-2b, chapter 3.55.4.1 (see Section 1.10.2 Cross Gateway Patient Discovery Request)38Section 1.10.26/27/22 3:54:39 PM by mbesnier
CH-XCPDCH-XCPD-004reviewedTestable 2 1 LivingSubjectId Parameter is the only required query Parameter. The following parameters of IHE ITI TF-2b, chapter 3.55.4.1.2.1 MAY be used (see Section 1.10.2.1 Major Components of the Patient Registry Query by Demographics)39Section 1.10.2.16/27/22 3:54:39 PM by aberge