Schema RequisitionWS.xsd


schema location:  ..\..\RequisitionWS.xsd
 
Elements 
SaveRequisitionAnyRequest 
SaveRequisitionAnyResponse 


element SaveRequisitionAnyRequest
diagram
children Document DocumentType MessageId
annotation
documentation 
Request for SaveRequisitionAny
source
<xs:element name="SaveRequisitionAnyRequest">
  <xs:annotation>
    <xs:documentation>Request for SaveRequisitionAny</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Document">
        <xs:annotation>
          <xs:documentation>The request/requisition document</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:any/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="DocumentType" type="xs:string" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Type of content in document. Only used if document type cannot be found automatically in the document.
Valid vaules are:
KITH1.3
KITH1.5
EHCM
Future expansion will be:
HL7</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="MessageId" type="xs:string" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Message id from sender

Only used/supported if LAB system can use it</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>

element SaveRequisitionAnyRequest/Document
diagram
annotation
documentation 
The request/requisition document
source
<xs:element name="Document">
  <xs:annotation>
    <xs:documentation>The request/requisition document</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:any/>
    </xs:sequence>
  </xs:complexType>
</xs:element>

element SaveRequisitionAnyRequest/DocumentType
diagram
type xs:string
annotation
documentation 
Type of content in document. Only used if document type cannot be found automatically in the document.
Valid vaules are:
KITH1.3
KITH1.5
EHCM
Future expansion will be:
HL7
source
<xs:element name="DocumentType" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Type of content in document. Only used if document type cannot be found automatically in the document.
Valid vaules are:
KITH1.3
KITH1.5
EHCM
Future expansion will be:
HL7</xs:documentation>
  </xs:annotation>
</xs:element>

element SaveRequisitionAnyRequest/MessageId
diagram
type xs:string
annotation
documentation 
Message id from sender

Only used/supported if LAB system can use it
source
<xs:element name="MessageId" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Message id from sender

Only used/supported if LAB system can use it</xs:documentation>
  </xs:annotation>
</xs:element>

element SaveRequisitionAnyResponse
diagram
children Status DocumentInfo AppRec
annotation
documentation 
Response for SaveRequisitionAny
source
<xs:element name="SaveRequisitionAnyResponse">
  <xs:annotation>
    <xs:documentation>Response for SaveRequisitionAny</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Status">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Delivered" type="xs:boolean"/>
            <xs:element name="ValidationPerformed" type="xs:boolean"/>
            <xs:element name="ValidationSuccessful" type="xs:boolean" minOccurs="0"/>
            <xs:element name="Message" type="xs:string" minOccurs="0">
              <xs:annotation>
                <xs:documentation>Message with status, warning or error regarding delivery and/or validation of message.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="DocumentInfo" minOccurs="0">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="ServiceProviderId" type="xs:string">
              <xs:annotation>
                <xs:documentation>Id for serviceprovider from the document in request, same as LabId. Used for routing document to correct database. 
E.g. TR_NSL, MO_SYMPATHY</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="LabType" type="xs:string" minOccurs="0">
              <xs:annotation>
                <xs:documentation>Lab type in document. Eg.g CLIN, MBIO .....</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="LabDocumentId" type="xs:string" minOccurs="0">
              <xs:annotation>
                <xs:documentation>Unique id for  LAB and report/request. 
Can be a combined id.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="RequestYear" type="xs:string">
              <xs:annotation>
                <xs:documentation>Request/Requisition year in document</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="RequestNumber" type="xs:string">
              <xs:annotation>
                <xs:documentation>Request/Requisition number in document</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="ProviderSystem" type="xs:string" minOccurs="0">
              <xs:annotation>
                <xs:documentation>E.g. SubSystem in NSL/NSML</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="ExternalId" type="xs:string">
              <xs:annotation>
                <xs:documentation>External id in document from sender linkin all document together. e.g. ActivityGUID in RoS</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="MessageId" type="xs:string" minOccurs="0">
              <xs:annotation>
                <xs:documentation>Message id from sender regarind the specific message/request saved.
Only used/supported if LAB system can use it</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="AppRec" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Application receipt in KITH format.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:any/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>

element SaveRequisitionAnyResponse/Status
diagram
children Delivered ValidationPerformed ValidationSuccessful Message
source
<xs:element name="Status">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Delivered" type="xs:boolean"/>
      <xs:element name="ValidationPerformed" type="xs:boolean"/>
      <xs:element name="ValidationSuccessful" type="xs:boolean" minOccurs="0"/>
      <xs:element name="Message" type="xs:string" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Message with status, warning or error regarding delivery and/or validation of message.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>

element SaveRequisitionAnyResponse/Status/Delivered
diagram
type xs:boolean
source
<xs:element name="Delivered" type="xs:boolean"/>

element SaveRequisitionAnyResponse/Status/ValidationPerformed
diagram
type xs:boolean
source
<xs:element name="ValidationPerformed" type="xs:boolean"/>

element SaveRequisitionAnyResponse/Status/ValidationSuccessful
diagram
type xs:boolean
source
<xs:element name="ValidationSuccessful" type="xs:boolean" minOccurs="0"/>

element SaveRequisitionAnyResponse/Status/Message
diagram
type xs:string
annotation
documentation 
Message with status, warning or error regarding delivery and/or validation of message.
source
<xs:element name="Message" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Message with status, warning or error regarding delivery and/or validation of message.</xs:documentation>
  </xs:annotation>
</xs:element>

element SaveRequisitionAnyResponse/DocumentInfo
diagram
children ServiceProviderId LabType LabDocumentId RequestYear RequestNumber ProviderSystem ExternalId MessageId
source
<xs:element name="DocumentInfo" minOccurs="0">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="ServiceProviderId" type="xs:string">
        <xs:annotation>
          <xs:documentation>Id for serviceprovider from the document in request, same as LabId. Used for routing document to correct database. 
E.g. TR_NSL, MO_SYMPATHY</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="LabType" type="xs:string" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Lab type in document. Eg.g CLIN, MBIO .....</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="LabDocumentId" type="xs:string" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Unique id for  LAB and report/request. 
Can be a combined id.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="RequestYear" type="xs:string">
        <xs:annotation>
          <xs:documentation>Request/Requisition year in document</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="RequestNumber" type="xs:string">
        <xs:annotation>
          <xs:documentation>Request/Requisition number in document</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="ProviderSystem" type="xs:string" minOccurs="0">
        <xs:annotation>
          <xs:documentation>E.g. SubSystem in NSL/NSML</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="ExternalId" type="xs:string">
        <xs:annotation>
          <xs:documentation>External id in document from sender linkin all document together. e.g. ActivityGUID in RoS</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="MessageId" type="xs:string" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Message id from sender regarind the specific message/request saved.
Only used/supported if LAB system can use it</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>

element SaveRequisitionAnyResponse/DocumentInfo/ServiceProviderId
diagram
type xs:string
annotation
documentation 
Id for serviceprovider from the document in request, same as LabId. Used for routing document to correct database. 
E.g. TR_NSL, MO_SYMPATHY
source
<xs:element name="ServiceProviderId" type="xs:string">
  <xs:annotation>
    <xs:documentation>Id for serviceprovider from the document in request, same as LabId. Used for routing document to correct database. 
E.g. TR_NSL, MO_SYMPATHY</xs:documentation>
  </xs:annotation>
</xs:element>

element SaveRequisitionAnyResponse/DocumentInfo/LabType
diagram
type xs:string
annotation
documentation 
Lab type in document. Eg.g CLIN, MBIO .....
source
<xs:element name="LabType" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Lab type in document. Eg.g CLIN, MBIO .....</xs:documentation>
  </xs:annotation>
</xs:element>

element SaveRequisitionAnyResponse/DocumentInfo/LabDocumentId
diagram
type xs:string
annotation
documentation 
Unique id for  LAB and report/request. 
Can be a combined id.
source
<xs:element name="LabDocumentId" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Unique id for  LAB and report/request. 
Can be a combined id.</xs:documentation>
  </xs:annotation>
</xs:element>

element SaveRequisitionAnyResponse/DocumentInfo/RequestYear
diagram
type xs:string
annotation
documentation 
Request/Requisition year in document
source
<xs:element name="RequestYear" type="xs:string">
  <xs:annotation>
    <xs:documentation>Request/Requisition year in document</xs:documentation>
  </xs:annotation>
</xs:element>

element SaveRequisitionAnyResponse/DocumentInfo/RequestNumber
diagram
type xs:string
annotation
documentation 
Request/Requisition number in document
source
<xs:element name="RequestNumber" type="xs:string">
  <xs:annotation>
    <xs:documentation>Request/Requisition number in document</xs:documentation>
  </xs:annotation>
</xs:element>

element SaveRequisitionAnyResponse/DocumentInfo/ProviderSystem
diagram
type xs:string
annotation
documentation 
E.g. SubSystem in NSL/NSML
source
<xs:element name="ProviderSystem" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>E.g. SubSystem in NSL/NSML</xs:documentation>
  </xs:annotation>
</xs:element>

element SaveRequisitionAnyResponse/DocumentInfo/ExternalId
diagram
type xs:string
annotation
documentation 
External id in document from sender linkin all document together. e.g. ActivityGUID in RoS
source
<xs:element name="ExternalId" type="xs:string">
  <xs:annotation>
    <xs:documentation>External id in document from sender linkin all document together. e.g. ActivityGUID in RoS</xs:documentation>
  </xs:annotation>
</xs:element>

element SaveRequisitionAnyResponse/DocumentInfo/MessageId
diagram
type xs:string
annotation
documentation 
Message id from sender regarind the specific message/request saved.
Only used/supported if LAB system can use it
source
<xs:element name="MessageId" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Message id from sender regarind the specific message/request saved.
Only used/supported if LAB system can use it</xs:documentation>
  </xs:annotation>
</xs:element>

element SaveRequisitionAnyResponse/AppRec
diagram
annotation
documentation 
Application receipt in KITH format.
source
<xs:element name="AppRec" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Application receipt in KITH format.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:any/>
    </xs:sequence>
  </xs:complexType>
</xs:element>


XML Schema documentation generated with
XML Spy Schema Editor www.xmlspy.com