element <dCustomConfiguration.CustomGroup>
Group Tag to hold custom information
Namespace:
http://www.nemsis.org
Type:
anonymous complexType
Content:
complex, 1 attribute, 6 elements
Defined:
locally within dCustomConfiguration complexType in dCustom_v3.xsd; see XML source
Includes:
definitions of 1 attribute, 6 elements
Content Model Diagram
XML Representation Summary
<dCustomConfiguration.CustomGroup
    CorrelationID
 = 
 xs:string
    >
   
Content: 
 dCustomConfiguration.01?, dCustomConfiguration.02?, dCustomConfiguration.03?, dCustomConfiguration.04?, dCustomConfiguration.05?, dCustomConfiguration.06*
</dCustomConfiguration.CustomGroup>
Content model elements (6):
dCustomConfiguration.01 (in dCustomConfiguration.CustomGroup),
dCustomConfiguration.02 (in dCustomConfiguration.CustomGroup),
dCustomConfiguration.03 (in dCustomConfiguration.CustomGroup),
dCustomConfiguration.04 (in dCustomConfiguration.CustomGroup),
dCustomConfiguration.05 (in dCustomConfiguration.CustomGroup),
dCustomConfiguration.06 (in dCustomConfiguration.CustomGroup)
Included in content model of elements (1):
dCustomConfiguration (in DEMDataSet)
XML Source (w/o annotations (7); see within schema source)
<xs:element id="dCustomConfiguration.dCustomGroup" maxOccurs="unbounded" minOccurs="0" name="dCustomConfiguration.CustomGroup">
<xs:complexType>
<xs:sequence>
<xs:element id="dCustomConfiguration.dCustomDataElementTitle" minOccurs="0" name="dCustomConfiguration.01" type="CustomTitle"/>
<xs:element id="dCustomConfiguration.dCustomDefinition" minOccurs="0" name="dCustomConfiguration.02" type="CustomDefinition"/>
<xs:element id="dCustomConfiguration.dCustomDataType" minOccurs="0" name="dCustomConfiguration.03" type="CustomDataType"/>
<xs:element id="dCustomConfiguration.dCustomDataElementRecurrence" minOccurs="0" name="dCustomConfiguration.04" type="YesNoValues"/>
<xs:element id="dCustomConfiguration.dCustomDataElementUsage" minOccurs="0" name="dCustomConfiguration.05" type="ElementUsage"/>
<xs:element id="dCustomConfiguration.dCustomDataElementPotentialValues" maxOccurs="unbounded" minOccurs="0" name="dCustomConfiguration.06">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="CustomValue"/>
</xs:simpleContent>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="CorrelationID" type="CorrelationID" use="optional"/>
</xs:complexType>
</xs:element>
Attribute Detail (all declarations; defined in this component only; 1/1)
CorrelationID
Type:
CorrelationID
Use:
optional
Attribute Value
xs:string
MaxLength:
 255
MinLength:
 0
XML Source (see within schema source)
<xs:attribute name="CorrelationID" type="CorrelationID" use="optional"/>
Content Element Detail (all declarations; defined in this component only; 6/6)
dCustomConfiguration.01
Type:
CustomTitle, simple content
<nemsisTacDoc> <number>dCustomConfiguration.01</number> <name>Custom Data Element Title</name> <national>No</national> <state>No</state> <definition>This is the title of the custom data element created to collect information that is not defined formally in NEMSIS Version 3.</definition> <v2Number/> <usage>Optional</usage> <performanceMeasure/> <comment>This is grouped with all data elements in this section and can have multiple instances.</comment> <v3Changes>Added to allow customized data elements to be inserted and collected from within the NEMSIS Version 3 standard.</v3Changes> </nemsisTacDoc>
Simple Content
xs:string
maxLength:
 100
minLength:
 2
XML Source (w/o annotations (1); see within schema source)
<xs:element id="dCustomConfiguration.dCustomDataElementTitle" minOccurs="0" name="dCustomConfiguration.01" type="CustomTitle"/>
dCustomConfiguration.02
Type:
CustomDefinition, simple content
<nemsisTacDoc> <number>dCustomConfiguration.02</number> <name>Custom Definition</name> <national>No</national> <state>No</state> <definition>The definition of the custom element and how it should be used.</definition> <v2Number/> <usage>Optional</usage> <performanceMeasure/> <comment/> <v3Changes/> </nemsisTacDoc>
Simple Content
xs:string
maxLength:
 255
minLength:
 0
XML Source (w/o annotations (1); see within schema source)
<xs:element id="dCustomConfiguration.dCustomDefinition" minOccurs="0" name="dCustomConfiguration.02" type="CustomDefinition"/>
dCustomConfiguration.03
Type:
CustomDataType, simple content
<nemsisTacDoc> <number>dCustomConfiguration.03</number> <name>Custom Data Type</name> <national>No</national> <state>No</state> <definition>The data type of the custom element.</definition> <v2Number/> <usage>Optional</usage> <performanceMeasure/> <comment/> <v3Changes/> </nemsisTacDoc>
Simple Content
enumeration of xs:string
Enumeration:
"9902001"
 - 
 Binary
"9902003"
 - 
 Date/Time
"9902005"
 - 
 Integer/Number
"9902007"
 - 
 Other (Not Listed)
"9902009"
 - 
 Text/String
XML Source (w/o annotations (1); see within schema source)
<xs:element id="dCustomConfiguration.dCustomDataType" minOccurs="0" name="dCustomConfiguration.03" type="CustomDataType"/>
dCustomConfiguration.04
Type:
YesNoValues, simple content
<nemsisTacDoc> <number>dCustomConfiguration.04</number> <name>Custom Data Element Recurrence</name> <national>No</national> <state>No</state> <definition>Indication if the data element will accept multiple values.</definition> <v2Number/> <usage>Optional</usage> <performanceMeasure/> <comment/> <v3Changes>Added to allow customized data elements to be inserted and collected from within the NEMSIS Version 3 standard.</v3Changes> </nemsisTacDoc>
Simple Content
enumeration of xs:string
Enumeration:
"9923001"
 - 
 No
"9923003"
 - 
 Yes
XML Source (w/o annotations (1); see within schema source)
<xs:element id="dCustomConfiguration.dCustomDataElementRecurrence" minOccurs="0" name="dCustomConfiguration.04" type="YesNoValues"/>
dCustomConfiguration.05
Type:
ElementUsage, simple content
<nemsisTacDoc> <number>dCustomConfiguration.05</number> <name>Custom Data Element Usage</name> <national>No</national> <state>No</state> <definition>The Usage (Mandatory, Required, Recommended, or Optional) for the Custom Data Element.</definition> <v2Number/> <usage>Optional</usage> <performanceMeasure/> <comment>Mandatory = Must be completed and will not accept null values <br/>Required = Must be completed but will accept null values <br/>Recommended = Not required but if collected will accept null values <br/>Optional = Not required but if collected, it cannot be a null value.</comment> <v3Changes>Added to allow customized data elements to be inserted and collected from within the NEMSIS Version 3 standard.</v3Changes> </nemsisTacDoc>
Simple Content
enumeration of xs:string
Enumeration:
"9903001"
 - 
 Mandatory
"9903003"
 - 
 Required
"9903005"
 - 
 Recommended
"9903007"
 - 
 Optional
XML Source (w/o annotations (1); see within schema source)
<xs:element id="dCustomConfiguration.dCustomDataElementUsage" minOccurs="0" name="dCustomConfiguration.05" type="ElementUsage"/>
dCustomConfiguration.06
Type:
anonymous (extension of CustomValue), simple content
<nemsisTacDoc> <number>dCustomConfiguration.06</number> <name>Custom Data Element Potential Values</name> <national>No</national> <state>No</state> <definition>The values which are associated with the Custom Data Element. Values would be the choices provided to the user when they document the Custom Data Element</definition> <v2Number/> <usage>Optional</usage> <performanceMeasure/> <comment/> <v3Changes>Added to allow customized data elements to be inserted and collected from within the NEMSIS Version 3 standard.</v3Changes> </nemsisTacDoc>
Simple Content
xs:string
maxLength:
 100
minLength:
 1
XML Source (w/o annotations (1); see within schema source)
<xs:element id="dCustomConfiguration.dCustomDataElementPotentialValues" maxOccurs="unbounded" minOccurs="0" name="dCustomConfiguration.06">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="CustomValue"/>
</xs:simpleContent>
</xs:complexType>
</xs:element>