Search Criteria : 18 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-PIXmCH-PIXm-001reviewedTestable 0 5 The PIX Consumer SHALL provide 1 or 2 Assigning Authorities for the Patient Identity Domains restricted to the assigning authority of the community and/or the EPR-SPID.25Table 3.83.4.1.2-15/31/21 2:43:38 PM by aeschlimann
CH-PIXmCH-PIXm-002reviewedTestable 0 5 The PIX Manager SHALL return at most 2 identifiers, with their assigning authorities (as specified in ITI TF - 2x: Appendix E.3).25Table 3.83.4.2.2-15/31/21 2:45:25 PM by aeschlimann
CH-PIXmCH-PIXm-003reviewedTestable 0 5 In the message response, the PIX Manager SHALL return at most 1 (one) Patient Ressource.25Table 3.83.4.2.2-15/31/21 2:43:25 PM by aeschlimann
CH-PIXmCH-PIXm-004reviewedTestable 0 6 The patient data SHALL be conform to the CH:PIXm Patient profile with the canonical url http://fhir.ch/ig/ch-epr-mhealth/StructureDefinition/ch-pixm-patient.22Section 3.3.65/31/21 2:43:26 PM by aeschlimann
CH-PIXmCH-PIXm-005reviewedTestable 0 5 If the patient is already registered in a community, the MPI-PID SHALL be provided as an identifier.22Section 3.3.65/31/21 2:43:28 PM by aeschlimann
CH-PIXmCH-PIXm-006reviewedTestable 0 5 If the patient is already registered in a community, the EPR-SPID MAY be added as an identifier in the Request.22Section 3.3.65/31/21 2:49:02 PM by aeschlimann
CH-PIXmCH-PIXm-007reviewedTestable 0 6 The birthname can be added to the Request with the ISO 21090 qualifier extension.22Section 3.3.65/31/21 2:50:36 PM by aeschlimann
CH-PIXmCH-PIXm-008reviewedTestable 0 6 The religion SHALL NOT be added to the request.22Section 3.3.65/31/21 2:50:46 PM by aeschlimann
CH-PIXmCH-PIXm-009reviewedTestable 0 5 If the MPI-PID is provided as an identifier, the PIX Manager SHALL use the MPI-PID to correlate the patient in the community.22Section 3.3.75/31/21 2:51:20 PM by aeschlimann
CH-PIXmCH-PIXm-010reviewedTestable 0 5 For the CH:PIXm Mobile Patient Identity Feed [ITI-93], TLS SHALL be used.23Section 3.3.95/31/21 2:52:03 PM by aeschlimann
CH-PIXmCH-PIXm-011reviewedTestable 0 5 The CH:PIXm Mobile Patient Identity Feed [ITI-93] request MUST authorize using the Incorporate Access Token [ITI-72] transaction of the IUA profile.23Section 3.3.95/31/21 2:52:00 PM by aeschlimann
ITI83ITI83-002reviewedTestable 0 5 In an ITI-83 query, the PIX Consumer SHALL provide exactly one instance of the sourceIdentifier.17Section 3.83.4.1.2.16/1/21 9:39:58 AM by aeschlimann
ITI83ITI83-004reviewedTestable 0 5 The Patient Identifier Cross-reference Manager SHALL use the sourceIdentifier and the targetSystem(s) parameters to determine the Patient Identities that match.18Section 3.83.4.1.36/1/21 9:42:30 AM by aeschlimann
ITI83ITI83-005reviewedTestable 0 5 In the query message, the PIX Consumer SHALL send 1 and only 1 identifier in the sourceIdentifier parameter.17Table 3.83.4.1.2-15/31/21 3:09:20 PM by aeschlimann
ITI83ITI83-007reviewedTestable 0 5 In the query message, the PIX Consumer SHALL send 0..1 _format parameter. This parameter defines the requested format of the response, from the mime-type value set.17Table 3.83.4.1.2-15/31/21 3:11:10 PM by aeschlimann
PIXmPIXm-001reviewedTestable 0 8 All the actors involved in the Patient Identity Cross-Referencing for mobile (PIXm) integration profile shall be grouped with the Time Client Actor.See ITI-TF Vol1 v17.0, page 316, Section 37.521Section 3.83.55/31/21 3:57:06 PM by aeschlimann
PIXmPIXm-002reviewedTestable 0 5 Patient Identifier Cross-Reference Consumer actor which claims support of the Patient Identity Cross-Referencing mobile (PIXm) integration profile shall perform the PIXm Query [ITI-83] transaction.10Figure 41.1-15/31/21 3:57:45 PM by aeschlimann
PIXmPIXm-003reviewedTestable 0 5 The patient identifier SHALL be represented as a root and an extension, where the root is an appropriately assigned OID.See ITI-TF Vol1 v17.0, page 246, Section 23.521Section 3.83.55/31/21 3:57:53 PM by aeschlimann