source: ccr/trunk/nhin-vista/projects/NHINC/Current/Product/Production/Gateway/NhinCA/src/jbiServiceUnits/NhinBPEL/META-INF/src/_references/_projects/Interfaces/src/wsdl/NhincComponentInternalSubDiscovery201309Orch.wsdl@ 507

Last change on this file since 507 was 507, checked in by George Lilly, 15 years ago

NHIN gateway and adaptor for use on linux with VistA EHR and RPMS
File size: 2.1 KB
Line 
1<?xml version="1.0" encoding="UTF-8"?>
2<definitions name="NhincComponentInternalSubDiscovery201309Orch" targetNamespace="http://j2ee.netbeans.org/wsdl/Interfaces/NhincComponentInternalSubDiscovery201309Orch"
3 xmlns="http://schemas.xmlsoap.org/wsdl/"
4 xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
5 xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://j2ee.netbeans.org/wsdl/Interfaces/NhincComponentInternalSubDiscovery201309Orch" xmlns:ns="urn:hl7-org:v3" xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype">
6 <types>
7 <xsd:schema targetNamespace="http://j2ee.netbeans.org/wsdl/Interfaces/NhincComponentInternalSubDiscovery201309Orch">
8 <xsd:import namespace="urn:hl7-org:v3" schemaLocation="../schemas/nhinc/hl7/HL7SubjectDiscoveryMessages.xsd"/>
9 </xsd:schema>
10 </types>
11 <message name="GetRealIdentRequestMessage">
12 <part name="GetRealIdentRequest" element="ns:PIXConsumer_PRPA_IN201309UVRequest"/>
13 </message>
14 <message name="GetRealIdentResponseMessage">
15 <part name="GetRealIdentResponse" element="ns:PIXConsumer_PRPA_IN201310UVRequest"/>
16 </message>
17 <portType name="NhincComponentInternalSubDiscovery201309OrchPortType">
18 <operation name="GetRealIdent">
19 <input name="GetRealIdentRequest" message="tns:GetRealIdentRequestMessage"/>
20 <output name="GetRealIdentResponse" message="tns:GetRealIdentResponseMessage"/>
21 </operation>
22 </portType>
23 <plnk:partnerLinkType name="NhincComponentInternalSubDiscovery201309Orch">
24 <!-- A partner link type is automatically generated when a new port type is added. Partner link types are used by BPEL processes.
25In 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.
26A partner link type characterizes the conversational relationship between two services. The partner link type can have one or two roles.-->
27 <plnk:role name="NhincComponentInternalSubDiscovery201309OrchPortTypeRole" portType="tns:NhincComponentInternalSubDiscovery201309OrchPortType"/>
28 </plnk:partnerLinkType>
29</definitions>
Note: See TracBrowser for help on using the repository browser.