...
The current encounter orchestrator will be extended to support CSD requests. Currently it makes custom request to a provider registry and a facility registry. We will update it to support querying of provider and facility information using the CSD mechanisms. This will be optional and the encounter orchestrator should be able to be configured as to how it communicates with the different registries.
To do this the encounter orchestrator would need to support two specific queries of the CSD Find Matching Services Request message.
Provider Search by ID
POST <location>/careServicesRequest
Accept: text/xml
Accept-Charset: utf-8
Content-Type: text/xml; charset=utf-8
Code Block | ||
---|---|---|
| ||
<?xml version="1" encoding="utf-8"?>
<careServicesRequest>
<function uuid="4e8bbeb9-f5f5-11e2-b778-0800200c9a66">
<requestParams>
<id oid="??">12345</id>
</requestParams>
</function>
</careServicesRequest> |
Facility Search by ID
POST <location>/careServicesRequest
Accept: text/xml
Accept-Charset: utf-8
Content-Type: text/xml; charset=utf-8
Code Block | ||
---|---|---|
| ||
<?xml version="1" encoding="utf-8"?>
<careServicesRequest>
<function uuid="c7640530-f600-11e2-b778-0800200c9a66">
<requestParams>
<otherID assigningAuthorityName="NID" code="NID">1234567890123456</otherID>
</requestParams>
</function>
</careServicesRequest> |