Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Note

Assertion should be change (3.5.4.UT.2 Unknown Stored Query) to expect error and not empty-registryList

Table of Contents

Overview

Verify Document Query search capability without mock-response and verify expected results, and verify Document Retrieve function.

Test Detail

The Document Query (Passthrough) service is running with JMX call script to set the CONNECT application to Passthrough services without application restart.

Document Query

  • Generate Patient ID (FullPatientID)

  • Send Document Query with search-parameter and verify the expected response.

Document Retrieve

  • Generate HCID (CorrectedLocalHCID)

  • Send Document Retrieve request and verify the expected response

DocQueryRetrieveSelfTest

Overview

The Test Suite verifies the success and failure response of data matching criteria for both services Document Query and Document Retrieve. The Test Suite is run in passthrough, the JMX script is to ensure that the service is in passthrough without the need for server restart.

Test Cases Detail for passthrough

The test cases verify specific matching criteria and assert expected response success or failure.

Document Query TestCases

  • 3.3.1.UT.2 - Find

...

Generate Patient ID for Doc Query

SOAP: Document Query

...

Assert status (Success)

...

  • by PatientId (single doc): matching patient id and return single document with success response

  • 3.3.2.UT.2 - Find

...

  1. Generate Patient ID for Doc Query

  2. Document Query

    • Assert status (Success)

    • Assert count (Document == 3)

...

  • by PatientId (multiple docs): matching patient id and return multiple documents with success response

  • 3.4.1.UT.1

...

Generate Patient ID for Doc Query

Document Query

...

Set invalid value (XDSDocumentEntryClassCode)

...

  • - No matching classcode: fail to match classcode and return success empty response

  • 3.4.1.UT.2

...

  1. Generate Patient ID for Doc Query

  2. Document Query

    • Set valid value (XDSDocumentEntryClassCode)

    • Assert status (Success)

    • Assert count (Document == 3)

...

  • - classcode one: a single classcode match with multiple documents in a successful response

  • 3.4.2.UT.2

...

Generate Patient ID for Doc Query

Document Query

...

Set invalid value (XDSDocumentEntryServiceStartTimeFrom, XDSDocumentEntryServiceStartTimeTo)

...

  • - no matching servicestarttime: fail to match document with service starttime from and to, return successful empty response

  • 3.4.2.UT.2

...

Generate Patient ID for Doc Query

Document Query

...

Set valid value (XDSDocumentEntryServiceStartTimeFrom, XDSDocumentEntryServiceStartTimeTo)

...

  • - matching service starttime: successful match with document on service starttime from and to, return document with successful response

  • 3.4.2.UT.2

...

  1. Generate Patient ID for Doc Query

  2. Document Query

    • Set valid value (XDSDocumentEntryServiceStartTimeFrom, XDSDocumentEntryServiceStartTimeTo)

    • Assert count (Document == 2)

    • Assert status (Success)

  • - matching service stoptime: successful match with document on service stoptime from and to, return documents with successful response

  • 3.4.3.UT.2

...

  1. Generate Patient ID for Doc Query

  2. Document Query

    • Set invalid value (XDSDocumentEntryCreationTimeFrom, XDSDocumentEntryCreationTimeTo)

    • Assert count (Document == 0)

  • - no matching creationtime between: fail to match document with creation time from and to, return successful empty response

  • 3.4.3.UT.2

...

  1. Generate Patient ID for Doc Query

  2. Document Query

    • Set valid value (XDSDocumentEntryCreationTimeFrom, XDSDocumentEntryCreationTimeTo)

    • Assert count (Document == 1)

    • Assert status (Success)

  • - creationtime between: successful match with document creation time from and to, return document with successful response

  • 3.4.3.UT.2

...

Generate Patient ID for Doc Query

Document Query

...

Set valid value (XDSDocumentEntryCreationTimeFrom, XDSDocumentEntryCreationTimeTo)

...

Assert count (Document == 1)

...

  • - creationtime left edge: successful match with document creation time from and to, return document with successful response

  • 3.4.3.UT.2

...

  1. Generate Patient ID for Doc Query

  2. Document Query

    • Set valid value (XDSDocumentEntryCreationTimeFrom, XDSDocumentEntryCreationTimeTo)

    • Assert count (Document == 1)

    • Assert status (Success)

  • - creationtime right edge: successful match with document creation time from and to, return document with successful response

  • 3.4.4.UT.2

...

  1. Generate Patient ID for Doc Query

  2. Document Query

    • Set valid value (XDSDocumentEntryClassCode, XDSDocumentEntryCreationTimeFrom, XDSDocumentEntryCreationTimeTo)

    • Assert count (Document == 1)

    • Assert status (Success)

3.4.4.UT.2 Class Code & Service Stop Time

  1. Generate Patient ID for Doc Query

  2. Document Query

    • Set valid value (XDSDocumentEntryClassCode, XDSDocumentEntryCreationTimeFrom, XDSDocumentEntryCreationTimeTo)

    • Assert count (Document == 2)

    • Assert status (Success)

  • - classCode & serviceStartTime: successful match with class code and service start time from and to, return document with successful response

  • 3.4.5.UT.2

...

  1. Generate Patient ID for Doc Query

  2. Document Query

    • Set valid value (XDSDocumentEntryServiceStartTimeFrom, XDSDocumentEntryServiceStartTimeTo, XDSDocumentEntryCreationTimeFrom, XDSDocumentEntryCreationTimeTo)

    • Assert count (Document == 1)

    • Assert status (Success)

  • - creationTime & serviceStartTime: successful match with creation time from and to, and service start time from and to, return document with successful response

  • 3.4.5.UT.2

...

  1. Generate Patient ID for Doc Query

  2. Document Query

    • Set valid value (XDSDocumentEntryServiceStartTimeFrom, XDSDocumentEntryServiceStartTimeTo, XDSDocumentEntryCreationTimeFrom, XDSDocumentEntryCreationTimeTo)

    • Assert count (Document == 1)

    • Assert status (Success)

  • - creationTime & serviceStopTime: successful match with creation time from and to, and service stop time from and to, return document with successful response

  • 3.4.6.UT.2

...

  1. Generate Patient ID for Doc Query

  2. Document Query

    • Set valid value (XDSDocumentEntryClassCode, XDSDocumentEntryCreationTimeFrom, XDSDocumentEntryCreationTimeTo)

    • Assert count (Document == 1)

    • Assert status (Success)

  • - creationtime & classCode: successful match with creation time from and to, and class code, return documents with successful response

  • 3.4.7.UT.2 - No Documents Available

...

  1. Generate Patient ID for Doc Query

  2. Document Query

    • Set PatientId with no document

    • Assert count (Document == 0)

  • : no document found patient Id and status type, return successful empty response

  • 3.5.2.UT.2 - No Patient Found

...

Generate Patient ID for Doc Query

Document Query

...

Set Invalid PatientID

...

  • : no patient found for patient id, return successful empty response

  • 3.5.4.UT.2 - Unknown Stored Query

...

  1. Generate Patient ID for Doc Query

  2. Document Query

    • Set Invalid ID (uuid)

    • Assert count (Document == 0)

    • Expect Error (Unknown Stored Query query id)

  • : fail to match store query id and return failure unknown stored query response

Document Retrieve TestCases

  • 11.3.1.UT.2 - Single

...

Generate HCID for Doc Retrieve

Document Retrieve

...

Assert Document (Document Id, HCID, Repository ID)

...

  • Doc: retrieve document with local Home Community ID (HCID), repository and document unique id with single document successful response.

  • 11.3.1.UT.4 - Document Persistence

...

  1. Generate HCID for Doc Retrieve

  2. Document Retrieve

    • Assert Document (Document Id, HCID, Repository ID)

    • Assert status (Success)

  • : retrieve document with local HCID, repository and document unique id with document successful response

  • 11.3.2.UT.2

...

  1. Generate HCID for Doc Retrieve

  2. Document Retrieve

    • Assert first Document (Document Id, HCID, Repository ID)

    • Assert second Document (Document Id, HCID, Repository ID)

    • Assert status (Success)

  • - Multiple Doc unique community ID one set: retrieving multiple document unique ids and expecting multiple documents in successful response

  • 11.4.1.UT.2

...

  1. Generate HCID for Doc Retrieve

  2. Document Retrieve

    1. Assert status (Failure)

11.3.2.UT.4 Multiple Documents Unique Community ID Multiple Set (Disabled)

  1. Initialize Configurations

  2. Generate HCID for Doc Retrieve

  3. Document Retrieve (Disabled)

3.5.11.UT.2 Missing Patient ID (Disabled)

  1. Initialize Configurations

  2. Document Query (Disabled)

3.5.1.UT.2 Too Many Results (Disabled)

...

Initialize Configurations

...

Generate Patient ID for Doc Query

...

  • - Missing Document: failure to match the document to document unique ids and return failure response