Difference between revisions of "MESA/Care Services Directory"

From IHE Wiki
Jump to navigation Jump to search
 
(27 intermediate revisions by the same user not shown)
Line 2: Line 2:
 
__TOC__
 
__TOC__
  
−
 
−
=Care Services Directory Tests=
 
−
=16600: CSD - Care Services Directory Test Data=
 
−
 
−
This is a "task" (ie not a test)  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/ 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 http://gazelle.ihe.net/SVSSimulator/browser/valueSetBrowser.seam]
 
−
 
−
<ul>
 
−
<li> 1.3.6.1.4.1.21367.200.101-CSD-organizationTypeCode.xml
 
−
<li> 1.3.6.1.4.1.21367.200.102-CSD-serviceTypeCode.xml
 
−
<li> 1.3.6.1.4.1.21367.200.103-CSD-facilityTypeCode.xml
 
−
<li> 1.3.6.1.4.1.21367.200.104-CSD-facilityStatusCode.xml
 
−
<li> 1.3.6.1.4.1.21367.200.105-CSD-providerTypeCode.xml
 
−
<li> 1.3.6.1.4.1.21367.200.106-CSD-providerStatusCode.xml
 
−
<li> 1.3.6.1.4.1.21367.200.108-CSD-credentialTypeCode.xml
 
−
<li> 1.3.6.1.4.1.21367.200.109-CSD-specializationTypeCode.xml
 
−
<li> 1.3.6.1.4.1.21367.200.110-CSD-languageCode.xml
 
−
</ul>
 
−
 
−
'''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=
 
=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.
+
This test description has moved here:  https://gazelle.ihe.net/content/mcsd-load-test-data
−
 
 
−
'''Instructions'''
 
−
 
 
−
<p><strong><span style="text-decoration: underline;">(1) Connectathon Organization, Provider, Facility, and Services entries</span></strong></p>
 
−
 
 
−
<p>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.&nbsp; Some Suppliers may support only a subset of these entry types.</p>
 
−
 
 
−
<p>We provide these Resources in XML format only.</p>
 
−
 
 
−
<p>'''Suppliers must load these Resources onto their test systems''' prior to performing mCSD Connectathon tests.  They are available in two places:</p>
 
−
 
 
−
<ol>
 
−
<li>On the IHE FTP site here: <b> ftp://ftp.ihe.net/Connectathon/test_data/ITI-profiles/mCSD-test-data/mCSD_FHIR-R4_Resources/ </b></li>
 
−
<li>During Conectathon wee:  On the FHIR Read/Write Server</li>
 
−
</ol>
 
−
 
 
−
<p><strong><span style="text-decoration: underline;">(2) Additional </span></strong><strong><span style="text-decoration: underline;">Organization, Provider, Facility, and Services entries</span></strong></p>
 
−
<p>The Connectathon entries are limited in scope. &nbsp;We expect Suppliers to be populated with additional Organization, Provider, Facility &amp; Service entries. &nbsp;We give no specific guidance on the number of entries, but we are looking for a more realistic database. &nbsp;Good entries offer better testing opportunities.</p>
 
−
 
 
−
<p><strong><span style="text-decoration: underline;">(2) Value Sets for some codes</span></strong>:</p>
 
−
 
 
−
<p>The FHIR Resources for mCSD testing contain links to value sets for some codes.</p>
 
−
<p>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</p>
 
−
 
 
−
<p>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. &nbsp;    They are available in the [https://gazelle.ihe.net/SVSSimulator/browser/valueSetBrowser.seam SVS Simulator]:</p>
 
−
<ul>
 
−
<li>'''Organization Type''' Codes:&nbsp; https://gazelle.ihe.net/SVSSimulator/rest/RetrieveValueSetForSimulator?id=1.3.6.1.4.1.21367.200.101</li>
 
−
<li>'''Service Type''' Codes:&nbsp; https://gazelle.ihe.net/SVSSimulator/rest/RetrieveValueSetForSimulator?id=1.3.6.1.4.1.21367.200.102</li>
 
−
<li>'''Facility Type''' Codes:&nbsp; https://gazelle.ihe.net/SVSSimulator/rest/RetrieveValueSetForSimulator?id=1.3.6.1.4.1.21367.200.103</li>
 
−
<li>'''Facility Status''' Codes (not used): 1.3.6.1.4.1.21367.200.104</li>
 
−
<li>'''Provider Type''' Codes:&nbsp; https://gazelle.ihe.net/SVSSimulator/rest/RetrieveValueSetForSimulator?id=1.3.6.1.4.1.21367.200.105</li>
 
−
<li>'''Provider Status''' Codes (not used): 1.3.6.1.4.1.21367.200.106</li>
 
−
<li>'''Credential Type''' Code:&nbsp; https://gazelle.ihe.net/SVSSimulator/rest/RetrieveValueSetForSimulator?id=1.3.6.1.4.1.21367.200.108</li>
 
−
<li>'''Specialty Type''' Codes:&nbsp; https://gazelle.ihe.net/SVSSimulator/rest/RetrieveValueSetForSimulator?id=1.3.6.1.4.1.21367.200.109</li>
 
−
</ul>
 
−
<p>These codes are also archived on the IHE FTP site [ftp://ftp.ihe.net/Connectathon/test_data/ITI-profiles/mCSD-test-data/mCSD_FHIR-R4_Resources/ here].</p>
 
−
<p>The Resources also reference these FHIR Value Sets:</p>
 
−
<ul>
 
−
<li>'''Language''' Codes: http://hl7.org/fhir/ValueSet/languages  (with coding.system of urn:ietf:bcp:47)</li>
 
−
<li>'''Provider Qualification''' Codes: https://www.hl7.org/fhir/v2/0360/2.7/index.html</li>
 
−
</ul>
 
−
 
 
−
'''Evaluation'''
 
−
 
 
−
Create a short text file saying that you have finished loading your codes.  Upload that text file into Gazelle Test Management as the results for this 'test'.  That is your signal to use that you are ready for Connectathon testing.
 

Latest revision as of 17:45, 14 October 2020

Audit Record Repository Test Cases


16610: mCSD - Care Services Selective Supplier Test Data

This test description has moved here: https://gazelle.ihe.net/content/mcsd-load-test-data

Retrieved from "http://wiki.ihe.net/index.php?title=MESA/Care_Services_Directory&oldid=123018"