Search Criteria : 26 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
ITI104ITI104-001validatedTestable 4 0 The Patient Identifier Cross-reference Manager shall only perform cross-referencing logic on messages received from Patient Identity Source Actors.1Section 2:3.104.4.1.16/14/22 5:03:38 PM by vhofman
ITI104ITI104-002validatedTestable 3 0 A Patient Identity Source initiates a FHIR request using Conditional Update as defined at http://hl7.org /fhir/http.html#cond-update on a Patient Resource.2Section 2:3.104.4.1.26/14/22 5:03:38 PM by vhofman
ITI104ITI104-003validatedTestable 3 0 A Patient Identity Source shall be able to send a request for either the JSON or the XML format as defined in FHIR. 2Section 2:3.104.4.1.26/14/22 5:03:38 PM by vhofman
ITI104ITI104-004validatedTestable 4 0 A Patient Identifier Cross-reference Manager shall be able to support the JSON and the XML format and support the conditional PUT operation.2Section 2:3.104.4.1.26/14/22 5:03:38 PM by vhofman
ITI104ITI104-005validatedTestable 3 0 The Patient Identity Source shall provide the identifier of the Patient Identification Domain of the Patient Identity Source.2Section 2:3.104.4.1.26/14/22 5:03:38 PM by vhofman
ITI104ITI104-006validatedTestable 3 0 The Patient Identifier Cross-reference Manager shall be capable of accepting elements specified in profile PIXm Patient: https://profiles.ihe.net/ITI/PIXm/StructureDefinition/IHE.PIXm.Patient.2Section 2:3.104.4.1.2.16/14/22 5:03:38 PM by vhofman
ITI104ITI104-007validatedTestable 3 0 If a Patient Identifier Cross-reference Manager constrains or specifies additional elements , it shall constrain the PIXm Patient profile see example and reference this as a supportedProfile in the CapabilityStatement.2Section 2:3.104.4.1.2.16/14/22 5:03:38 PM by vhofman
ITI104ITI104-008validatedTestable 3 0 The Patient Identifier Cross-reference Manager shall provide a CapabilityStatement with the capabilities interaction and indicate that conditionalUpdate is available on the Patient.2Section 2:3.104.4.1.36/14/22 5:03:38 PM by vhofman
ITI104ITI104-009validatedTestable 2 0 A Patient Identifier Cross-reference Manager shall support the Conditional Update based on the identifier parameter as outlined in http://hl7.org/fhir/http.html#cond-update.2Section 2:3.104.4.1.36/14/22 5:03:38 PM by vhofman
ITI104ITI104-010validatedNot testable 0 0 The Patient Identifier Cross-reference Manager shall only recognize a single Patient Identity Source per domain.2Section 2:3.104.4.1.36/27/22 3:54:39 PM by vhofman
ITI104ITI104-011validatedTestable 2 0 Once the Patient Identifier Cross-reference Manager has completed its cross-referencing function, it shall make the newly cross-referenced identifiers available to PIX queries.2Section 2:3.104.4.1.36/14/22 5:03:38 PM by vhofman
ITI104ITI104-012validatedTestable 3 0 A Patient Identity Source shall be able to send a request for either the JSON or the XML format as defined in FHIR.4Section 2:3.104.4.2.26/14/22 5:03:38 PM by vhofman
ITI104ITI104-013validatedTestable 3 0 A Patient Identifier Cross-reference Manager shall be able to support the JSON and the XML format and support the conditional PUT operation.4Section 2:3.104.4.2.26/14/22 5:03:38 PM by vhofman
ITI104ITI104-014validatedTestable 3 0 The Patient Identifier Cross-reference Manager shall provide a CapabilityStatement with the capabilities interaction and indicate that conditionalUpdate is available on the Patient.4Section 2:3.104.4.2.36/14/22 5:03:38 PM by vhofman
ITI104ITI104-015validatedTestable 2 0 When the Patient Identifier Cross-reference Manager receives the Resolve Duplicate Patient message it shall replace any references it is maintaining internally to the subsumed patient identifier with the patient identifier in the replaced-by link.4Section 2:3.104.4.2.36/14/22 5:03:38 PM by vhofman
ITI104ITI104-016validatedTestable 2 0 After the identifier references are replaced, the Patient Identifier Cross-reference Manager shall reapply its internal cross-referencing logic/ policies before providing the updated information via the PIX Query transactions.4Section 2:3.104.4.2.36/14/22 5:03:38 PM by vhofman
ITI104ITI104-017validatedTestable 1 0 A Patient Identity Source initiates a FHIR request using HTTP DELETE as defined at 3.1.0.7.1 Conditional delete on a Patient Resource based on the identifier parameter.5Section 2:3.104.4.3.26/14/22 5:06:07 PM by vhofman
ITI104ITI104-018validatedTestable 2 0 A Patient Identity Source shall be able to send a request for either the JSON or the XML format as defined in FHIR.5Section 2:3.104.4.3.26/14/22 5:03:38 PM by vhofman
ITI104ITI104-019validatedTestable 1 0 A Patient Identifier Cross-reference Manager shall be able to support the JSON and the XML format and support the conditional DELETE operation if it supports the Remove Patient message.5Section 2:3.104.4.3.26/14/22 5:06:18 PM by vhofman
ITI104ITI104-020validatedTestable 3 0 See ITI TF-2: Appendix Z.8 Mobile Security Considerations, which includes guidance on the use of ATNA and IUA to protect the communication, access control, and audit logging.5Section 2:3.104.56/14/22 5:03:38 PM by vhofman