Diagnostic

Diagnostics from vehicle service associated with sublet.
                    

Element information

Content

• Sequence [1..1]
  from type IdentificationType
  ID [0..*]    Is the Identifiers of the given instance of an entity within the scope of the integration. The schemeAgencyID attribute identifies the party that provided or knows this party by the given identifier.
  IDSet [0..*]    
  from type DiagnosticBaseType
  Code [0..*]    Element for the communication of all codes.
  Symptom [0..*]    This identifies the symptoms that are associated with a problem
  Remedy [0..*]    This identifies a Remedy for a specific problem
  Failure [0..*]    Information on the problem, possible symptoms that may lead to the problem, and the cause and remedy for the problem. Causes and/or remedies could be reported against a failure in a multi-level hierarchical reporting. For example, failure analysis could be recorded as follows; for failure A, causes P and Q are the factors and remedies X, Y and Z are to be taken.
  1. Extension [0..1]    Allows the user of OAGIS to extend the specification in order to provide additional information that is not captured in OAGIS.This is done by defining the additional information in XML Schema and referencing the new schema in the xml instance document through the use of namespaces. Once this is done the additional information defined there can be carried in the BOD XML instance document.The Open Applications Group will make best efforts to quickly consider all proposed submissions.The Extension is always the last element in all components, except where the component has been extended inline.

Attributes

Used in

• Type SubletBaseType
• Type SubletType via extension of SubletBaseType (Element Sublet)

Sample instance

<Diagnostic>
   <ID/>
   <IDSet>
      <ID/>
   </IDSet>
   <Code/>
   <Symptom>
      <ID/>
      <IDSet>
         <ID/>
      </IDSet>
      <Description/>
      <Note/>
      <Extension>
         <AnyExtension>
            <!--any element-->
         </AnyExtension>
         <Amount/>
         <Code/>
         <DateTime></DateTime>
         <ID/>
         <Indicator>true</Indicator>
         <Measure/>
         <Name/>
         <Number>1.0</Number>
         <Quantity/>
         <Text/>
         <Time></Time>
         <ValueText>string</ValueText>
      </Extension>
   </Symptom>
   <Remedy>
      <ID/>
      <IDSet>
         <ID/>
      </IDSet>
      <Description/>
      <Note/>
      <Extension>
         <AnyExtension>
            <!--any element-->
         </AnyExtension>
         <Amount/>
         <Code/>
         <DateTime></DateTime>
         <ID/>
         <Indicator>true</Indicator>
         <Measure/>
         <Name/>
         <Number>1.0</Number>
         <Quantity/>
         <Text/>
         <Time></Time>
         <ValueText>string</ValueText>
      </Extension>
   </Remedy>
   <Failure>
      <ID/>
      <IDSet>
         <ID/>
      </IDSet>
      <Problem>
         <ID/>
         <IDSet>...
         </IDSet>
         <Description/>
         <Note/>
         <Symptom>...
         </Symptom>
         <Cause>...
         </Cause>
         <Remedy>...
         </Remedy>
         <Extension>.......................................
         </Extension>
      </Problem>
      <Extension>
         <AnyExtension>
            <!--any element-->
         </AnyExtension>
         <Amount/>
         <Code/>
         <DateTime></DateTime>
         <ID/>
         <Indicator>true</Indicator>
         <Measure/>
         <Name/>
         <Number>1.0</Number>
         <Quantity/>
         <Text/>
         <Time></Time>
         <ValueText>string</ValueText>
      </Extension>
   </Failure>
   <Extension>
      <AnyExtension>
         <!--any element-->
      </AnyExtension>
      <Amount/>
      <Code/>
      <DateTime></DateTime>
      <ID/>
      <Indicator>true</Indicator>
      <Measure/>
      <Name/>
      <Number>1.0</Number>
      <Quantity/>
      <Text/>
      <Time></Time>
      <ValueText>string</ValueText>
   </Extension>
</Diagnostic>