> For the complete documentation index, see [llms.txt](https://help.santesuite.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.santesuite.org/installation/installation-1/deployment/installing-software/santedb-server/installation-qualification/fhir-interface-validation/mpi-cr-test-cases-for-hl7v2/test-ohie-cr-17-hl7v2.md). # TEST: OHIE-CR-17-HL7v2 This test will ensure that the client registry appropriately handles a merge condition whereby the local authority has not assigning authority to perform or merge the identifiers provided. This test will also ensure that merges across assigning authorities cannot be performed ## References ## Pre-Conditions / Setup #### Setup the receiver so that OID 2.16.840.1.113883.3.72.5.9.2 has assigning authority of TEST\_A which can be assigned from TEST\_HARNESS\_A #### Setup the receiver so that OID 2.16.840.1.113883.3.72.5.9.3 has assigning authority of TEST\_B which can be assigned from TEST\_HARNESS\_B #### Ensure that the following patient is registered in the receiver (can be done with the ADT message provided). Name: Sam Smith, id: RJ-203^^^TEST\_A, gender: F, dob: 1989-02-25 ``` MSH|^~\&|TEST_HARNESS_A^^|TEST^^|CR1^^|MOH_CAAT^^|20141104174451||ADT^A01^ADT_A01|TEST-CR-17-15|P|2.3.1 EVN||20101020 PID|||RJ-203^^^TEST_A||SMITH^SAM^^^^^L||19890225|F||||||||||| PV1||I ``` #### Ensure that the following patient is registered in the receiver (can be done with the ADT message provided). Name: Samantha Smith, id: RJ-292^^^TEST\_A, gender: F, dob: 1989-02 ``` MSH|^~\&|TEST_HARNESS_A^^|TEST^^|CR1^^|MOH_CAAT^^|20141104174451||ADT^A01^ADT_A01|TEST-CR-17-20|P|2.3.1 EVN||20101020 PID|||RJ-292^^^TEST_A||SMITH^SAMANTHA^^^^^L||198902|F||||||||||| PV1||I ``` #### Ensure that the following patient is registered in the receiver (can be done with the ADT message provided). Name: Samantha Smith, id: SJ-204^^^TEST\_B, gender: F, dob: 1989-02 ``` MSH|^~\&|TEST_HARNESS_B^^|TEST^^|CR1^^|MOH_CAAT^^|20141104174451||ADT^A01^ADT_A01|TEST-CR-17-25|P|2.3.1 EVN||20101020 PID|||SJ-204^^^TEST_B||SMITH^SAMANTHA^^^^^L||198902|F||||||||||| PV1||I ``` ## Test Step 1: Test harness (as TEST\_HARNESS\_B) sends ADT^A40 message attempting to merge identities from TEST\_A domain. ``` MSH|^~\&|TEST_HARNESS_B^^|TEST^^|CR1^^|MOH_CAAT^^|20141104174451||ADT^A40^ADT_A40|TEST-CR-17-30|P|2.3.1 EVN||20101020 PID|||RJ-203^^^TEST_A||SMITH^SAM^^^^^L||198902|F||||||||||| MRG|RJ-292^^^TEST_A ``` ### Expected Behaviour * Receiver rejects message with an AE * MSH-5 and MSH-6 matches “TEST\_HARNESS\_B|TEST” * An ERR segment exists identifying the error ## Test Step 2: Test harness (as TEST\_HARNESS\_B) sends ADT^A40 message attempting to merge across domains by instructing the receiver to merge an identifier from TEST\_A into TEST\_B. ``` MSH|^~\&|TEST_HARNESS_B^^|TEST^^|CR1^^|MOH_CAAT^^|20141104174451||ADT^A40^ADT_A40|TEST-CR-17-40|P|2.3.1 EVN||20101020 PID|||SJ-204^^^TEST_B||SMITH^SAM^^^^^L||198902|F||||||||||| MRG|RJ-292^^^TEST_A ``` ### Expected Behaviour * Receiver rejects message with an AE or AR * MSH-5 and MSH-6 matches “TEST\_HARNESS\_B|TEST” * An ERR segment exists identifying the error ## Test Step 3: Test harness (as TEST\_HARNESS\_B) sends ADT^A40 message attempting to merge a patient identifier which does not exist. ``` MSH|^~\&|TEST_HARNESS_B^^|TEST^^|CR1^^|MOH_CAAT^^|20141104174451||ADT^A40^ADT_A40|TEST-CR-17-50|P|2.3.1 EVN||20101020 PID|||SJ-204^^^TEST_B||SMITH^SAM^^^^^L||198902|F||||||||||| MRG|RJ-292^^^TEST_B ``` ### Expected Behaviour * Receiver rejects message with an AE or AR * MSH-5 and MSH-6 matches “TEST\_HARNESS\_B|TEST” * An ERR segment exists identifying the error with HL7 code of 204 (key does not exist) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.santesuite.org/installation/installation-1/deployment/installing-software/santedb-server/installation-qualification/fhir-interface-validation/mpi-cr-test-cases-for-hl7v2/test-ohie-cr-17-hl7v2.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.