MESA/Care Services Directory

From IHEWiki

Jump to: navigation, search

Audit Record Repository Test Cases

Contents


Care Services Directory Tests

16600: CSD - Care Services Directory Test Data

This is not an actual "test". Rather it is a task that ensures that your CSD Care Services Directory is loaded with the entries that we will use as part of Connectathon testing.

Reference

ITI TF-1:35.1.1.1 states, "Implementing jurisdictions may mandate code sets for Organization Type, Service Type, Facility Type, Facility Status, Provider Type, Provider Status, Contact Point Type, Credential Type, Specialization Code, and language code. A Care Services Directory actors shall be configurable to use these codes, where mandated."

Instructions

For connectathon testing, we define these codes and ask that you load them onto your directory prior to arriving at the connectathon. They are documented in the format defined in IHE's SVS (Sharing Value Sets) profile, though support for SVS is not mandated in IHE.

The code sets are archived here: ftp://ftp.ihe.net/Connectathon/test_data/ITI-profiles/CSD-test-data/. They are also available in the SVS Simulator: http://gazelle.ihe.net/SVSSimulator/browser/valueSetBrowser.seam

  • 1.3.6.1.4.1.21367.200.101-CSD-organizationTypeCode.xml
  • 1.3.6.1.4.1.21367.200.102-CSD-serviceTypeCode.xml
  • 1.3.6.1.4.1.21367.200.103-CSD-facilityTypeCode.xml
  • 1.3.6.1.4.1.21367.200.104-CSD-facilityStatusCode.xml
  • 1.3.6.1.4.1.21367.200.105-CSD-providerTypeCode.xml
  • 1.3.6.1.4.1.21367.200.106-CSD-providerStatusCode.xml
  • 1.3.6.1.4.1.21367.200.108-CSD-credentialTypeCode.xml
  • 1.3.6.1.4.1.21367.200.109-CSD-specializationTypeCode.xml
  • 1.3.6.1.4.1.21367.200.110-CSD-languageCode.xml

Evaluation

Create a short text file saying that you have finished loading your codes. Upload that text file into gazelle as the results for this 'test'. That is your signal to use that you are ready for Connectathon testing.

16610: mCSD - Care Services Selective Supplier Test Data

This is not an actual "test". Rather it is a task that ensures that your mCSD Care Services Selective Supplier is loaded with the entries that we will use as part of Connectathon testing.

Instructions

(1) Connectathon Organization, Provider, Facility, and Services entries

In order to perform query testing with predictable results, Care Services Selective Supplier must be populated with the entries from pre-defined FHIR Resources for Organizations, Locations, HealthcareServices, Practitioners, and PractitionerRoles.  Some Suppliers may support only a subset of these entry types.

We provide these Resources in XML format only.

Suppliers must load these Resources onto their test systems prior to performing mCSD Connectathon tests. They are available in two places:

  1. On the IHE FTP site here: ftp://ftp.ihe.net/Connectathon/test_data/ITI-profiles/mCSD-test-data/FHIR_Resources/
  2. On the Connectathon FHIR Server

(2) Additional Organization, Provider, Facility, and Services entries

The Connectathon entries are limited in scope.  We expect Directories to be populated with additional Organization, Provider, Facility & Service entries.  We give no specific guidance on the number of entries, but we are looking for a more realistic database.  Good entries offer better testing opportunities.

(2) Value Sets for some codes:

The FHIR Resources for mCSD testing contain links to value sets for some codes.

These value sets are hosted on the Gazelle SVS Simulator tool, enabling use of a URL to point to the value set from within FHIR Resources

For connectathon testing, we define these codes. They are documented in the format defined in IHE's SVS (Sharing Value Sets) profile, though support for SVS is not mandated in IHE.   They are available in the SVS Simulator:

These codes are also archived on the IHE FTP site here.

The Resources also reference these FHIR Value Sets:

Evaluation

Create a short text file saying that you have finished loading your codes. Upload that text file into gazelle as the results for this 'test'. That is your signal to use that you are ready for Connectathon testing.

Personal tools