Office of Court Administration Automated Registry (AR) Interface Design Document for DSHS - Clinical Management for Behavioral Health Services (CMBHS)

Transcription

1 Office of Court Administration Automated Registry (AR) Interface Design Document for DSHS - Clinical Management for Behavioral Health Services (CMBHS) August 04, 2009 Interface Design Document for CMBHS 1 of 27

2 Contents 1. Revision History 4 2. Introduction Purpose Assumptions and Constraints Requirements Implementation Design Static View Dynamic View Error Handling Security Network Authentication Audit Tracking Data Retention Data Design DSHS-CMBHS Transaction CMBHS Web Service Methods Error Message Formats DSHS-CMBHS Code Tables Gender Race Match Type Interface Design Document for CMBHS 2 of 27

3 5. Deployment Design Issues/Questions Glossary References CMBHS Webservice File (WSDL) Interface Design Document for CMBHS 3 of 27

4 1. Revision History Version Date Name Description /26/2008 Faizal Pakrudeen /10/2009 Jeff Corn First Draft Created with Questions based on the agency meeting 11/13/2008 Revised draft based on agency meeting (03/27/2009), provided WSDL, and correspondence on specific questions. 1 04/13/2009 Paul Falkenberg Final Edits and Formatting /13/2009 Thomas Sullivan OCA and DSHS edits /29/2009 Jeff Corn Accepted the changes/feedback from the client /30/2009 Jeff Corn Modified Section Race Code Table /04/2009 Jeff Corn Modified Section Race Code Table Interface Design Document for CMBHS 4 of 27

5 2. Introduction The Interface Design Document provides the details of the DSHS-CMBHS Interface for Automated Registry (AR) System. The AR System will interface with the DSHS-CMBHS data source to query the data from the data source mentioned below. Clinical Management for Behavioral Health Services (CMBHS): A clinical management system containing information about a consumer s mental health treatments. This information will be used for providing for the continuity of care and/or case management. The CMBHS system provides mental health information including Most Recent Date of Treatment, Current Provider, Diagnosis, Mental Health History, Alerts (future capability) and Drug Treatment. 2.1 Purpose This document lays out the interface details, including the design aspects of the adapters that connect to the DSHS-CMBHS data source, details about the needed transactions, data formats involved in various transactions between the AR System and the DSHS-CMBHS System and security design aspects of the interface. 2.2 Assumptions and Constraints The table below lists the Assumptions and Constraints made for the Interface Design for the DSHS-CMBHS Interface. Number Assumption/Constraint This document assumes the interface to CMBHS data source will meet the requirement The technical low-level design aspect of the CMBHS Webservice based Adapter will be part of the AR Software Architecture Document. 2.3 Requirements This document provides the details of the interface between the AR System and the DSHS- CMBHS data source, a requirement stated in the OCA Request for Offers for Automated Registry System (Final Offer). Number Requirement The system must interface with the following mandatory data sources: The Texas Department of State Health Services CMBHS system Interface Design Document for CMBHS 5 of 27

6 3. Implementation Design The AR System will query the CMBHS data source using a Webservice based adapter. The WS Adapter s Webservice client will invoke the query request method exposed in the WSDL. The CMBHS Webservice implementation will process the request message and return the response message to the AR system. The interface will request the individual information based on provided search criteria. The CMBHS will perform the search based on its algorithms and return the request to the AR System. The AR system will convert the query result to NIEM based XML format and display the results to the user. 3.1 Static View The Static View demonstrates the various components involved in the DSHS-CMBHS Interface. Microsoft Biztalk Server AR Security Active Directory Certificate Authority Authorized Personnel Token MSAD Two Factor Authentication AR Query Portal Microsoft IIS ASP.NET AR Integration Broker Microsoft BizTalk Server 2006R2.NET 2.0 AR MetaStore Database BizTalk MessageBox Microsoft SQL Server 2005 WS Client CMBHS Adapter WSDL CMBHS Webservices DSHS- CMBHS System TXOCA-Automated Registry The AR System user will be authenticated using a two-factor authentication mechanism. Using a token-based authentication, the AR System user will be directed to the AR Login page. In the AR Query Portal, the user will be authenticated based on an active directory user ID and Password and the user can issue an Identifier-based query for the allowed query types for that user. The CMBHS adapter s Webservice client will invoke the methods exposed in the WSDL. The CMBHS Webservice implementation will in turn query the CMBHS Oracle database and return the results. The AR System will compile the results and display the Query Responses to the AR System User in a well defined format. Interface Design Document for CMBHS 6 of 27

7 3.2 Dynamic View The AR Query System will interface to the DSHS-CMBHS data source through the CMBHS Adapter. This adapter is a webservice based adapter. This distributed query data flow between the AR and DSHS-CMBHS is explained below. The following diagram shows the distributed query flow between AR System and the CMBHS System. Authorized User Web Browser 1 OCA - AR Hub DSHS-CMBHS AR Query Portal 2 Send Port Request Metadata AR BizTalk Server CMBHS Adapter DSHS- CMBHS 4 4 AR Metastore Database AR SQL Server 6 Receive Port 5 AR Security Active Directory, CA, SSL Query Result Step 1: When a user attempts to access the AR Query Portal, a logon page welcomes the user and presents them with a form to enter their user name and password. The system validates the user s credentials against the central active directory and caches the user authorization privileges. This information is used throughout the session to define what this user is allowed to do or what data they are allowed to see. The user s role defined in the Active Directory will specify which systems he or she can query and what data they can see. The user enters the query criteria and submits the query. Step 2: The AR Query Portal collects the person query search criteria. Step 3: The CMBHS Adapter s webservice client will call the method exposed in WSDL and will pass search parameters entered by the user Step 4: The CMBHS Webservices will process the request and return the result to the receive port of the WS adapter. Step 5: The CMBHS adapter will get the results and convert the results to a common format. Step 6: The CMBHS Adapter writes the response message to the AR meta-store database. Interface Design Document for CMBHS 7 of 27

8 Step 7: The AR Query Portal s Web application displays the aggregated query results to the user. Step 8: The AR System updates the AR Meta-Store Database s SQL Server table with the Audit data related to the Query. 3.3 Error Handling The AR System will have an Error Handling Mechanism that handles the Error Messages from the DSHS-CMBHS System. If the AR System receives an Error Message as response to a Query Request, the AR System will clean up the entire transaction that is associated with that Query. The CMBHS Webservices will respond with the SOAP Exceptions for the following cases: Soap Header Authentication failures service account (User ID/Password) incorrect, etc. Web Method Parameters failures If the parameters passed to the method are not valid, a data rejected error message will be send by the CMBHS Web service. CMBHS Application Errors If any application errors behind the CMBHS Webservices occur (like DB connection failures, timeouts, etc), then an appropriate error message will be sent by the CMBHS Webservice. Finally, if the CMBHS Webservice is unable to find a record matching the query criteria then the CMBHS System will send a response indicating no record found. 3.4 Security The CMBHS can be accessed through an existing SOAP WS-I Basic Profile. The AR system will be provided a single service account (user name and password) for all Webservice calls to the CMBHS system. This service account will passed in SOAP header of every webservice call. The AR system will access the CMBHS Webservices using an HTTPS connection Network The DSHS-CMBHS System will be accessible from Texas OCA AR System using a public HTTPS connection. (The Server Name and URL details will be updated later.) System Server Name URL Authentication The AR System will send a single Service Account (user-id and password) as part of the SOAP header. Interface Design Document for CMBHS 8 of 27

9 3.4.3 Audit Tracking The AR System will keep the Audit data related to a query transaction between the AR System and the DSHS-CMBHS System. The audit records will cover the information mentioned in the table below. Data Element User ID Reason Date/Time Stamp of send Date/Time Stamp of received Query String Data Sources Queried Query Type Transaction Transaction Description The User ID who sent the Query The Reason for the Query The Date/Time Stamp of the Query Request The Date/Time Stamp of the Query Response This field will contain the Query Criteria used for a specific query. The name of the data source The AR System Query Type used for the transaction. The AR System will maintain the Audit Trail for each transaction. Audit records will be kept for a minimum of one year. Finally, the AR System will send the AR User ID (Active Directory User ID) along with the search criteria to the CMBHS Webservice calls, supporting CMBHS audit trails for users performing queries Data Retention The AR System will retain the Query Results data while the User Session is active. This information is stored temporarily and discarded once the user ends the session or the session times out. Interface Design Document for CMBHS 9 of 27

10 4. Data Design 4.1 DSHS-CMBHS Transaction This section covers the CMBHS Inquiry message formats and its response formats. The AR System will access DSHS-CMBHS information through a name based query to obtain a pick list and then use an identifier to obtain the detailed information. The CMBHS adapter will aggregate data from the CMBHS Webservices and provide the AR System with a result set. The details of the request and response data elements are described in the subsections below CMBHS Web Service Methods The CMBHS Inquiry is used to obtain the mental health information of an individual. The AR system will collect all query criteria entered by the user and pass them as parameters to a webservice method exposed in the WSDL and invoke that method. CMBHS Webservice Methods ProcessClientMatch (TLETSQueryMessage) : TLETSQueryResponseMessage Interface Design Document for CMBHS 10 of 27

11 Web Method ProcessClientMatch Below are the request and response messages for the webservice method Web Method ProcessClientMatch (Request Message Format) The following table shows the details of the request methods exposed in the WSDL. TLETSQueryMessage Field(s) Data Type(s) Description/Edits TLETSQueryMessage Complex Version String Version Information. Example: <?xml version=\"1.0\" encoding=\"utf- 8\"?> <TLETSQueryMessage xmlns:xsi=\" Schema-instance\" xmlns:xsd=\" LSchema\" xmlns=\" hs/\"> Initiator String Constant value = OCA Destination String Constant value = DSHS ControlField String Not used. Leave blank UserID String AR User ID performing the query Alphanumeric; Max Length = 255 QueryID String AR Query ID (GUID) associated with the query Alphanumeric; Max Length = 255 QueryTime DateTime The date and time the query is sent. Format: CCYY-MM-DDTHH:MI:SS Interface Design Document for CMBHS 11 of 27

12 Example: T09:02:30 Note: The Hours is 1-24 hour scale. FacilityName String AR system is not using. Leave Blank FacilityStreetAddress String AR system is not using. Leave Blank FacilityCity String AR system is not using. Leave Blank FacilityZip String AR system is not using. Leave Blank FacilityCountyCode String AR system is not using. Leave Blank FacilityContactPersonName String AR system is not using. Leave Blank String AR system is not using. Leave Blank FacilityContactPhoneNumber FirstName String First Name of the Individual Alphanumeric; Max Length = 50 LastName String Last Name of the Individual Alphanumeric; Max Length = 50 SSN String Social Security Number Num(9) - Numeric values only converted to a string data type. Example: DateofBirth DateTime Date of Birth Format: CCYY-MM-DDTHH:MI:SS Example: T0000:00 Note: The time portion will be zeros. Gender String See Code Table values (Section 4.2) CMBHS value will be sent and received. Interface Design Document for CMBHS 12 of 27

13 Race String See Code Table values (Section 4.2) CMBHS value will be sent and received Web Method ProcessClientMatch (Response Message Format) The response message will be in SOAP based XML format. The response message will have a SOAP header and followed by the response data elements. TLETSQueryResponseMessage Field(s) Data Type(s) Description/Edits TLETSQueryResponseMessa ge Complex Version String Version Information. Example: <?xml version=\"1.0\" encoding=\"utf- 8\"?> <TLETSQueryResponseMessage xmlns:xsi=\" Schema-instance\" xmlns:xsd=\" LSchema\" xmlns=\" hs/\"> Initiator String Constant value = OCA Destination String Constant value = DSHS ControlField String Not used. Leave blank UserID String AR User ID performing the query Alphanumeric; Max Length = 255 QueryID String AR Query ID (GUID) associated with the query Alphanumeric; Max Length = 255 QueryTime DateTime The date and time the query is sent. Interface Design Document for CMBHS 13 of 27

14 Format: CCYY-MM-DDTHH:MI:SS Example: T09:02:30 Note: The Hours is 1-24 hour scale. FacilityName String AR system is not using. Leave Blank FacilityStreetAddress String AR system is not using. Leave Blank FacilityCity String AR system is not using. Leave Blank FacilityZip String AR system is not using. Leave Blank FacilityCountyCode String AR system is not using. Leave Blank FacilityContactPersonName String AR system is not using. Leave Blank String AR system is not using. Leave Blank FacilityContactPhoneNumber FirstName String First Name of the Individual Alphanumeric; Max Length = 50 LastName String Last Name of the Individual Alphanumeric; Max Length = 50 SSN String Social Security Number Num(9) - Numeric values only converted to a string data type. Example: DateofBirth DateTime Date of Birth Format: CCYY-MM-DDTHH:MI:SS Example: T0000:00 Note: The time portion will be zeros. Interface Design Document for CMBHS 14 of 27

15 Gender String See Code Table values (Section 4.2) Race String See Code Table values (Section 4.2) ErrorMessage String If any errors occur on the CMBHS WebService, the error messages will be sent back in this field. Alphanumeric; Max Length = 255 BusyMessage String CMBHS is not using this field. TLETSResponse ArrayOfPerson See below complex XML Element ArrayOfPerson Complex CMBHSID Int CMBHS Unique ID for Person Record AR System is not using. MatchType String See Code Table values (Section 4.2) CMBHS value will be sent and received. LastName String Last Name of the Individual Alphanumeric; Max Length = 50 FirstName String First Name of the Individual Alphanumeric; Max Length = 50 MiddleName String Middle Name of the Individual Alphanumeric; Max Length = 50 SSN String Social Security Number Format: Num(9) - Numeric values only converted to a string data type Example: DateofBirth DateTime Date of Birth Interface Design Document for CMBHS 15 of 27

16 Format: CCYY-MM-DDTHH:MI:SS Example: T0000:00 Note: The time portion will be zeros. Gender String See Code Table values (Section 4.2) CMBHS value will be sent and received. Race String See Code Table values (Section 4.2) CMBHS value will be sent and received. County String County of the individual Alphanumeric; Max Length = 50 FacilityName String The Facility where the Individual is/was located. Alphanumeric; Max Length = 80 PhoneNumber String Phone Number Numeric; Max Length = 10 CaseID String The Case Number associated with the Individual. Alphanumeric; Max Length = 20 Interface Design Document for CMBHS 16 of 27

17 4.1.2 Error Message Formats The Error Message formats that will be used to handle the various Exceptions during the transactions are mentioned below. The errors will be sent back to the AR System in the returned XML (TLETSQueryResponse ErrorMessage field) Error Message Formats (Response Error Messages) Some example error messages are in the table below. Response Fields ErrorMessage ErrorMessage ErrorMessage Description/Edits User not authenticated or not successfully loaded from DB Authentication header needs to be provided for authorization Gender in the request has to be 'male' or 'female'. Interface Design Document for CMBHS 17 of 27

18 4.2 DSHS-CMBHS Code Tables This section covers the CMBHS Code Table values used in the request and/or response message exchanges. The tables below contain the CMBHS values and Descriptions. Any message exchanges requiring these code values between AR & CMBHS will be translate the system specific values as required. Note: The AR & CMBHS Code Table value translations will be defined in the Use Case as some code tables may be used across multiple interfaces. This document will only define the CMBHS values. The details of the request and response data elements are described in the subsections below Gender The Gender code table has different types of individual genders supported by the CMBHS System. Please see the Use Case for system to system value translations. CMBHS Value male female Description Male Female Race The Race code table has different ethnic types listed and supported by the CMBHS System. Please see the Use Case for system to system value translations. CMBHS Value American Indian or Alaskan Native Asian Black or African American Native Hawaiian or Pacific Islander White Unknown Description American Indian or Alaskan Native Asian Black or African American Native Hawaiian or Pacific Islander White Unknown Match Type The Match Type code table will have values that indicate whether the individual search found the person or not. These matches will vary depending on the search criteria. Please see the Use Case for system to system value translations. CMBHS Value E P Description An Exact match was found. *** See Match Rules below. A Probable match was found. Interface Design Document for CMBHS 18 of 27

19 *** See Match Rules below. Interface Design Document for CMBHS 19 of 27

20 Match Rule Definition(s) Logic performed by CMBHS WebService Exact Match Data Inquiry matches the following combination: o Combination # 1 Last Name First Name Date of Birth Gender Social Security Number Race Probable Match Data Inquiry matches on one of the following combinations: o Combination # 1 Last Name First Name Initial Date of Birth Gender o Combination # 2 Last Name First Name Initial Date of Birth Year only (will extract from input DOB) Gender Social Security Number o Combination # 3 Last Name First 3 letters First Name Initial Date of Birth Year & Month only (will extract from input DOB) Gender Social Security Number o Combination # 4 Last Name (Note: Matches to any others found) First Name Initial (Note: Matches to any other found) Date of Birth (Note: current Age calculation is within 5 years) Gender Social Security Number (Note: Matches to any others found) Note: AR System will always pass the entire DOB, not partials. The CMBHS Service will extract Year, Month, etc as required to perform the search as outlined in logic above. Interface Design Document for CMBHS 20 of 27

21 5. Deployment Design The OCA will host the AR System in various environments and communicate with the DSHS-CMBHS over public HTTPS connection. The following table will outline the various environments. Environment AR (IP Address / Port) CMBHS System (URL / Port) Integration System Test Pilot User Acceptance Production 6. Issues/Questions # Issue/Question Status Interface Design Document for CMBHS 21 of 27

22 7. Glossary Term AR System CMBHS OCA DSHS SOAP WS WSDL Definition Automated Registry System Clinical Management for Behavioral Health Services Office of Courts Administration Department of State Health Services Simple Object Access Protocol Webservice Webservice Definition Language Interface Design Document for CMBHS 22 of 27

23 8. References This section provides a complete list of all documents referenced elsewhere in the Interface Design Document. No. Reference Title Version [1] OCA Request for Offers for Automated Registry System (Final Offer). [2] WDSL provide by CMBHS agency (see below) Interface Design Document for CMBHS 23 of 27

24 8.1 CMBHS Webservice File (WSDL) <?xml version="1.0" encoding="utf-8"?> - <wsdl:definitions xmlns:soap=" xmlns:tm=" xmlns:soapenc=" xmlns:mime=" xmlns:tns=" xmlns:s=" xmlns:soap12=" xmlns:http=" targetnamespace=" xmlns:wsdl=" - <wsdl:types> - <s:schema elementformdefault="qualified" targetnamespace=" - <s:element name="processclientmatch"> - <s:complextype> - <s:sequence> <s:element minoccurs="0" maxoccurs="1" name="tletsquerymessagerequest" type="tns:tletsquerymessage" /> </s:sequence> </s:complextype> </s:element> - <s:complextype name="tletsquerymessage"> - <s:sequence> <s:element minoccurs="0" maxoccurs="1" name="version" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="initiator" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="destination" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="controlfield" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="userid" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="queryid" type="s:string" /> <s:element minoccurs="1" maxoccurs="1" name="querytime" type="s:datetime" /> <s:element minoccurs="0" maxoccurs="1" name="facilityname" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="facilitystreetaddress" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="facilitycity" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="facilityzip" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="facilitycountycode" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="facilitycontactpersonname" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="facilitycontactphonenumber" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="firstname" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="lastname" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="ssn" type="s:string" /> <s:element minoccurs="1" maxoccurs="1" name="dateofbirth" type="s:datetime" /> <s:element minoccurs="0" maxoccurs="1" name="gender" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="race" type="s:string" /> </s:sequence> </s:complextype> - <s:element name="processclientmatchresponse"> - <s:complextype> - <s:sequence> <s:element minoccurs="0" maxoccurs="1" name="processclientmatchresult" type="tns:tletsqueryresponsemessage" /> </s:sequence> </s:complextype> </s:element> - <s:complextype name="tletsqueryresponsemessage"> - <s:sequence> <s:element minoccurs="0" maxoccurs="1" name="version" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="initiator" type="s:string" /> Interface Design Document for CMBHS 24 of 27

25 <s:element minoccurs="0" maxoccurs="1" name="destination" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="controlfield" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="userid" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="queryid" type="s:string" /> <s:element minoccurs="1" maxoccurs="1" name="querytime" type="s:datetime" /> <s:element minoccurs="0" maxoccurs="1" name="facilityname" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="facilitystreetaddress" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="facilitycity" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="facilityzip" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="facilitycountycode" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="facilitycontactpersonname" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="facilitycontactphonenumber" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="firstname" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="lastname" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="ssn" type="s:string" /> <s:element minoccurs="1" maxoccurs="1" name="dateofbirth" type="s:datetime" /> <s:element minoccurs="0" maxoccurs="1" name="gender" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="race" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="tletsresponse" type="tns:arrayofperson" /> <s:element minoccurs="0" maxoccurs="1" name="errormessage" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="busymessage" type="s:string" /> </s:sequence> </s:complextype> - <s:complextype name="arrayofperson"> - <s:sequence> <s:element minoccurs="0" maxoccurs="unbounded" name="person" nillable="true" type="tns:person" /> </s:sequence> </s:complextype> - <s:complextype name="person"> - <s:sequence> <s:element minoccurs="1" maxoccurs="1" name="cmbhsid" type="s:int" /> <s:element minoccurs="0" maxoccurs="1" name="matchtype" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="lastname" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="firstname" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="middlename" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="ssn" type="s:string" /> <s:element minoccurs="1" maxoccurs="1" name="dateofbirth" type="s:datetime" /> <s:element minoccurs="0" maxoccurs="1" name="gender" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="race" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="county" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="facilityname" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="phonenumber" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="caseid" type="s:string" /> </s:sequence> </s:complextype> <s:element name="cmbhsauthenticationheader" type="tns:cmbhsauthenticationheader" /> - <s:complextype name="cmbhsauthenticationheader"> - <s:sequence> <s:element minoccurs="0" maxoccurs="1" name="cmbhsusername" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="cmbhspassword" type="s:string" /> </s:sequence> <s:anyattribute /> </s:complextype> </s:schema> </wsdl:types> - <wsdl:message name="processclientmatchsoapin"> <wsdl:part name="parameters" element="tns:processclientmatch" /> </wsdl:message> Interface Design Document for CMBHS 25 of 27

26 - <wsdl:message name="processclientmatchsoapout"> <wsdl:part name="parameters" element="tns:processclientmatchresponse" /> </wsdl:message> - <wsdl:message name="processclientmatchcmbhsauthenticationheader"> <wsdl:part name="cmbhsauthenticationheader" element="tns:cmbhsauthenticationheader" /> </wsdl:message> - <wsdl:porttype name="clientmatchservicesoap"> - <wsdl:operation name="processclientmatch"> <wsdl:documentation xmlns:wsdl=" generic request for data from CMBHS</wsdl:documentation> <wsdl:input message="tns:processclientmatchsoapin" /> <wsdl:output message="tns:processclientmatchsoapout" /> </wsdl:operation> </wsdl:porttype> - <wsdl:binding name="clientmatchservicesoap" type="tns:clientmatchservicesoap"> <soap:binding transport=" /> - <wsdl:operation name="processclientmatch"> <soap:operation soapaction=" style="document" /> - <wsdl:input> <soap:body use="literal" /> <soap:header message="tns:processclientmatchcmbhsauthenticationheader" part="cmbhsauthenticationheader" use="literal" /> </wsdl:input> - <wsdl:output> <soap:body use="literal" /> <soap:header message="tns:processclientmatchcmbhsauthenticationheader" part="cmbhsauthenticationheader" use="literal" /> </wsdl:output> </wsdl:operation> </wsdl:binding> - <wsdl:binding name="clientmatchservicesoap12" type="tns:clientmatchservicesoap"> <soap12:binding transport=" /> - <wsdl:operation name="processclientmatch"> <soap12:operation soapaction=" style="document" /> - <wsdl:input> <soap12:body use="literal" /> <soap12:header message="tns:processclientmatchcmbhsauthenticationheader" part="cmbhsauthenticationheader" use="literal" /> </wsdl:input> - <wsdl:output> <soap12:body use="literal" /> <soap12:header message="tns:processclientmatchcmbhsauthenticationheader" part="cmbhsauthenticationheader" use="literal" /> </wsdl:output> </wsdl:operation> </wsdl:binding> - <wsdl:service name="clientmatchservice"> - <wsdl:port name="clientmatchservicesoap" binding="tns:clientmatchservicesoap"> <soap:address location=" ce.asmx" /> </wsdl:port> - <wsdl:port name="clientmatchservicesoap12" binding="tns:clientmatchservicesoap12"> <soap12:address location=" ce.asmx" /> </wsdl:port> Interface Design Document for CMBHS 26 of 27

27 </wsdl:service> </wsdl:definitions> Interface Design Document for CMBHS 27 of 27