[507] | 1 | <?xml version="1.0" encoding="UTF-8"?>
|
---|
| 2 | <definitions name="AdapterMpiManager" targetNamespace="urn:gov:hhs:fha:nhinc:adaptermpimanager"
|
---|
| 3 | xmlns="http://schemas.xmlsoap.org/wsdl/"
|
---|
| 4 | xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
|
---|
| 5 | xmlns:xsd="http://www.w3.org/2001/XMLSchema"
|
---|
| 6 | xmlns:tns="urn:gov:hhs:fha:nhinc:adaptermpimanager"
|
---|
| 7 | xmlns:hl7="urn:hl7-org:v3"
|
---|
| 8 | xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
|
---|
| 9 | <types>
|
---|
| 10 | <xsd:schema targetNamespace="urn:gov:hhs:fha:nhinc:adaptermpimanager">
|
---|
| 11 | <xsd:import namespace="urn:hl7-org:v3" schemaLocation="../schemas/HL7V3/multicacheschemas/MCCI_IN000002UV01.xsd"/>
|
---|
| 12 | <xsd:import namespace="urn:hl7-org:v3" schemaLocation="../schemas/HL7V3/multicacheschemas/PRPA_IN201301UV.xsd"/>
|
---|
| 13 | <xsd:import namespace="urn:hl7-org:v3" schemaLocation="../schemas/HL7V3/multicacheschemas/PRPA_IN201303UV.xsd"/>
|
---|
| 14 | </xsd:schema>
|
---|
| 15 | </types>
|
---|
| 16 | <message name="AddPatientRequestMessage">
|
---|
| 17 | <part name="AddPatientRequest" element="hl7:PRPA_IN201301UV"/>
|
---|
| 18 | </message>
|
---|
| 19 | <message name="AddPatientResponseMessage">
|
---|
| 20 | <part name="AddPatientResponse" element="hl7:MCCI_IN000002UV01"/>
|
---|
| 21 | </message>
|
---|
| 22 | <message name="RemovePatientRequestMessage">
|
---|
| 23 | <part name="RemovePatientRequest" element="hl7:PRPA_IN201303UV"/>
|
---|
| 24 | </message>
|
---|
| 25 | <message name="RemovePatientResponseMessage">
|
---|
| 26 | <part name="RemovePatientResponse" element="hl7:MCCI_IN000002UV01"/>
|
---|
| 27 | </message>
|
---|
| 28 | <portType name="AdapterMpiManagerPortType">
|
---|
| 29 | <operation name="AddPatient">
|
---|
| 30 | <input name="AddPatientRequest" message="tns:AddPatientRequestMessage"/>
|
---|
| 31 | <output name="AddPatientResponse" message="tns:AddPatientResponseMessage"/>
|
---|
| 32 | </operation>
|
---|
| 33 | <operation name="RemovePatient">
|
---|
| 34 | <input name="RemovePatientRequest" message="tns:RemovePatientRequestMessage"/>
|
---|
| 35 | <output name="RemovePatientResponse" message="tns:RemovePatientResponseMessage"/>
|
---|
| 36 | </operation>
|
---|
| 37 | </portType>
|
---|
| 38 | <binding name="AdapterMpiManagerPortTypeBinding" type="tns:AdapterMpiManagerPortType">
|
---|
| 39 | <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
|
---|
| 40 | <operation name="AddPatient">
|
---|
| 41 | <soap:operation style="document" soapAction="urn:AddPatient"/>
|
---|
| 42 | <input name="AddPatientRequest">
|
---|
| 43 | <soap:body use="literal"/>
|
---|
| 44 | </input>
|
---|
| 45 | <output name="AddPatientResponse">
|
---|
| 46 | <soap:body use="literal"/>
|
---|
| 47 | </output>
|
---|
| 48 | </operation>
|
---|
| 49 | <operation name="RemovePatient">
|
---|
| 50 | <soap:operation style="document" soapAction="urn:RemovePatient"/>
|
---|
| 51 | <input name="RemovePatientRequest">
|
---|
| 52 | <soap:body use="literal"/>
|
---|
| 53 | </input>
|
---|
| 54 | <output name="RemovePatientResponse">
|
---|
| 55 | <soap:body use="literal"/>
|
---|
| 56 | </output>
|
---|
| 57 | </operation>
|
---|
| 58 | </binding>
|
---|
| 59 | <service name="AdapterMpiManagerService">
|
---|
| 60 | <port name="AdapterMpiManagerPortTypeBindingPort" binding="tns:AdapterMpiManagerPortTypeBinding">
|
---|
| 61 | <soap:address location="http://localhost:${NhincHttpPort}/AdapterMpiManagerService"/>
|
---|
| 62 | </port>
|
---|
| 63 | </service>
|
---|
| 64 | <plnk:partnerLinkType name="AdapterMpiManager">
|
---|
| 65 | <!-- A partner link type is automatically generated when a new port type is added. Partner link types are used by BPEL processes.
|
---|
| 66 | In a BPEL process, a partner link represents the interaction between the BPEL process and a partner service. Each partner link is associated with a partner link type.
|
---|
| 67 | A partner link type characterizes the conversational relationship between two services. The partner link type can have one or two roles.-->
|
---|
| 68 | <plnk:role name="AdapterMpiManagerPortTypeRole" portType="tns:AdapterMpiManagerPortType"/>
|
---|
| 69 | </plnk:partnerLinkType>
|
---|
| 70 | </definitions>
|
---|