D02A
Message D02A/DMRDEF
Data maintenance request definition message
This Data maintenance request definition message (DMRDEF) permits the transfer of a data maintenance request action among parties involved in the preparation, processing, assessment, resolution and directory production processes.
Message description
UNH
M(1) : Message headerA service segment starting and uniquely identifying a message. The message type code for the Data maintenance request definition message is DMRDEF. Note: Data maintenance request definition messages conforming to this document must contain the following data in segment UNH, composite S009: Data element 0065 DMRDEF 0052 D 0054 02A 0051 UN
BGM
M(1) : Beginning of messageA segment to indicate the beginning of the message and to transmit function, type and number of the message.
DII
M(1) : Directory identificationA segment specifying the identity of the reference directory set used in creating the DMR.
DTM
M(9) : Date/time/periodA segment specifying date information, e.g., the date the submitter forwarded the DMR, preparation date, technical assessment review date, final approval date, etc. Date information is to be provided in CCYYMMDD format.
FTX
M(99) : Free textA segment specifying text information outlining the business requirement for this DMR. This segment may also be used by the originating technical assessment group to convey any explanations or comments which should accompany the DMR through the international assessment process. Other assessment groups will comment on a DMR via the DMSTAT message.
RFF
C(999) : ReferenceA segment identifying the type of and reference log number of this request, as well as any related DMRs. In order to ensure proper identification of related DMRs, this segment shall identify, if existing, any parent and child DMRs one level above or below the current level. This segment shall not identify grand-parents and grand-children at any level. (Although a related DMR may have multiple parent DMRs and/or multiple child DMRs, the parent and child DMRs for these related DMRs will not be identified in the current DMR.) A related DMR(s) at the highest level, will have no parent DMR(s). A related DMR(s) at the lowest level will have no child DMR(s). The actual DMR reference log number type may be: Original submitter, Entry point assessment log number, Central secretariat log number, or International assessment log number. The related reference log number type may be: Original submitter, parent DMR Original submitter, child DMR Entry point assessment log number, parent DMR Entry point assessment log number, child DMR Central secretariat log number, parent DMR Central secretariat log number, child DMR International assessment log number, parent DMR International assessment log number, child DMR Also, the submitter must identify a message design group with which the DMR should be associated. This message design group will be consulted by technical assessment for functional evaluations.
EFI
C(9) : External file link identificationA segment identifying associated documentation, including document reference and document type.
SG1 M(99) : PNA-ADR-SG2
A group of segments identifying the party(ies) filing the Data maintenance request. In case of a jointly submitted DMR all parties shall be identified.
PNA
M(1) : Party identificationA segment identifying the originator of the Data maintenance request, e.g., the DMR submitter, Secretariat, etc. At least one occurrence is required to identify the submitter's organization name. When forwarding a DMR to the central secretariat the sender must identify which entry point is forwarding the DMR.
ADR
C(1) : AddressA segment identifying the DMR originator's address information.
SG2 C(9) : CTA-COM
A group of segments identifying the DMR originator's communication type(s) and number(s).
CTA
M(1) : Contact informationA segment identifying a person or a department for the party specified in the leading PNA segment to whom the communication should be directed.
COM
C(9) : Communication contactA segment identifying communication type(s) and number(s) of person(s) or department(s) specified in the associated CTA segment.
SG3 M(1) : MSG-ATT-FTX-SG4-SG6
A group of segments providing a message type directory.
MSG
M(1) : Message type identificationA segment identifying a message type to be specified.
ATT
C(99) : AttributeA segment used to specify if the message is for use with the batch or interactive message directories. It also may indicate what modifications the DMR will make to the message.
FTX
C(999) : Free textA segment providing textual information related to the message type, namely: Message type name, Introduction, Scope, Functional definition, Field of application, Principles, References, Terms and definitions, Standard terms and definitions, and Message terms and conditions.
SG4 C(999) : SGU-ATT-FTX-SG5
A group of segments specifying a message type structure and its related functional definition.
SGU
M(1) : Segment usage detailsA segment specifying the usage of a segment in a message type structure. The segment names for component segments are to be defined in the segment identification segment group. The segment names are provided once for each segment tag in the message and are the basis for all occurrences of the segment name in the message boilerplate.
ATT
C(9) : AttributeA segment to indicate what modifications the DMR will make to the clarification text for the segment.
FTX
C(99) : Free textA segment providing textual information about segment usage. This information comprises part of the data segment clarification section.
SG5 C(1) : GRU-ATT-FTX
A group of segments identifying a segment group and providing details about segment group usage.
GRU
M(1) : Segment group usage detailsA segment specifying the usage of a segment group in a message type structure.
ATT
C(9) : AttributeA segment to indicate what modifications the DMR will make to the segment group's clarification text.
FTX
C(99) : Free textA segment providing the textual information about segment group usage. This information comprises part of the data segment clarification section.
SG6 C(99) : FNT-REL-GIR-ATT-FTX
A group of segments to provide the relationship of segments and/or segment groups through dependency notes or other notes about the usage of segments or segment groups at identified positions in the message.
FNT
M(1) : FootnoteA segment to provide the footnote identification for a dependency note or other note to be applied against one or more segments and/or segment groups of a message.
REL
C(1) : RelationshipA segment to provide the type of dependency relationship, where one exists.
GIR
C(9) : Related identification numbersA segment to provide the position number(s) for segments and/or segment groups to which a note applies.
ATT
C(9) : AttributeA segment to provide the change indicators at the note level.
FTX
C(9) : Free textA segment to provide free text for a position relative note.
SG7 C(9999) : SEG-ATT-FTX-ELU-SG8
A group of segments providing a segment directory.
SEG
M(1) : Segment identificationA segment identifying a segment type and specifying its class and maintenance operation.
ATT
C(9) : AttributeA segment used to indicate what modifications the DMR will make to the segment.
FTX
C(9) : Free textA segment specifying the name and functional definition of a segment type.
ELU
C(99) : Data element usage detailsA segment specifying the simple and/or component data elements in a segment type. The component element names are to be defined in either the composite data element identification segment group or the simple data element identification segment group, as appropriate for the component structure. The component element names are provided once for each component element tag in the segment and are the basis for all occurrences of the component element name in the segment structure.
SG8 C(99) : FNT-REL-GIR-ATT-FTX
A group of segments to provide the relationship of composites and/or simple data elements through dependency notes or other notes about the usage of elements at identified positions in the segment.
FNT
M(1) : FootnoteA segment to provide the footnote identification for a dependency note or other note to be applied against one or more elements of a segment.
REL
C(1) : RelationshipA segment to provide the type of dependency relationship, where one exists.
GIR
C(9) : Related identification numbersA segment to provide the position number(s) for composites and/or simple data elements to which a note applies.
ATT
C(9) : AttributeA segment to provide the change indicators at the note level.
FTX
C(9) : Free textA segment to provide free text for a position relative note.
SG9 C(9999) : CMP-ATT-FTX-ELU-SG10
A group of segments providing a composite data element directory.
CMP
M(1) : Composite data element identificationA segment identifying a composite data element and specifying its class and maintenance operation.
ATT
C(9) : AttributeA segment used to indicate what modifications the DMR will make to the composite.
FTX
C(9) : Free textA segment specifying the name and functional definition of a composite data element type.
ELU
C(99) : Data element usage detailsA segment specifying component data elements in a composite data element and its related information. The simple data element names are to be given in the simple data element identification segment group. The simple data element names are provided once for each simple data element tag in the composite and are the basis for all occurrences of the simple data element name in the composite structure.
SG10 C(99) : FNT-REL-GIR-ATT-FTX
A group of segments to provide the relationship of simple data elements through dependency notes or other notes about the usage of the elements at identified positions in the composite.
FNT
M(1) : FootnoteA segment to provide the footnote identification for a dependency note or other note to be applied against one or more elements of a composite.
REL
C(1) : RelationshipA segment to provide the type of dependency relationship, where one exists.
GIR
C(9) : Related identification numbersA segment to provide the position number(s) for simple data elements to which a note applies.
ATT
C(9) : AttributeA segment to provide the change indicators at the note level.
FTX
C(9) : Free textA segment to provide free text for a position relative note.
SG11 C(9999) : ELM-ATT-FTX
A group of segments providing a data element directory.
ELM
M(1) : Simple data element detailsA segment identifying a simple data element and giving related information.
ATT
C(9) : AttributeA segment used to indicate what modifications the DMR will make to the simple data element.
FTX
C(9) : Free textA segment specifying the name and functional definition of a simple data element.
SG12 C(9999) : CDS-FTX-SG13
A group of segments providing a code list directory.
CDS
M(1) : Code set identificationA segment specifying a code set.
FTX
C(9) : Free textA segment providing textual information related to the code list.
SG13 C(9999) : CDV-ATT-FTX
A group of segments specifying a code value and its functional definition.
CDV
M(1) : Code value definitionA segment specifying a code value. In DMRDEF use the associated free text segment to provide the code value's name.
ATT
C(9) : AttributeA segment used to indicate what modifications the DMR will make to the code.
FTX
C(9) : Free textA segment specifying the name and functional definition of a code value.
UNT
M(1) : Message trailerA service segment ending a message, giving the total number of segments in the message (including the UNH & UNT) and the control reference number of the message.
Message structure
UNH, Message header M 1 BGM, Beginning of message M 1 DII, Directory identification M 1 DTM, Date/time/period M 9 FTX, Free text M 99 RFF, Reference C 999 EFI, External file link identification C 9 --- Segment Group 1 ------------------------- M 99 -------+ PNA, Party identification M 1 | ADR, Address C 1 | | --- Segment Group 2 ------------------------- C 9 ------+| CTA, Contact information M 1 || COM, Communication contact C 9 || ---- ----------------------------------------------------------++ --- Segment Group 3 ------------------------- M 1 -------+ MSG, Message type identification M 1 | ATT, Attribute C 99 | FTX, Free text C 999 | | --- Segment Group 4 ------------------------- C 999 ------+| SGU, Segment usage details M 1 || ATT, Attribute C 9 || FTX, Free text C 99 || || --- Segment Group 5 ------------------------- C 1 -----+|| GRU, Segment group usage details M 1 ||| ATT, Attribute C 9 ||| FTX, Free text C 99 ||| ---- ---------------------------------------------------------++| | --- Segment Group 6 ------------------------- C 99 ------+| FNT, Footnote M 1 || REL, Relationship C 1 || GIR, Related identification numbers C 9 || ATT, Attribute C 9 || FTX, Free text C 9 || ---- ----------------------------------------------------------++ --- Segment Group 7 ------------------------- C 9999 -------+ SEG, Segment identification M 1 | ATT, Attribute C 9 | FTX, Free text C 9 | ELU, Data element usage details C 99 | | --- Segment Group 8 ------------------------- C 99 ------+| FNT, Footnote M 1 || REL, Relationship C 1 || GIR, Related identification numbers C 9 || ATT, Attribute C 9 || FTX, Free text C 9 || ---- ----------------------------------------------------------++ --- Segment Group 9 ------------------------- C 9999 -------+ CMP, Composite data element identification M 1 | ATT, Attribute C 9 | FTX, Free text C 9 | ELU, Data element usage details C 99 | | --- Segment Group 10 ------------------------ C 99 ------+| FNT, Footnote M 1 || REL, Relationship C 1 || GIR, Related identification numbers C 9 || ATT, Attribute C 9 || FTX, Free text C 9 || ---- ----------------------------------------------------------++ --- Segment Group 11 ------------------------ C 9999 -------+ ELM, Simple data element details M 1 | ATT, Attribute C 9 | FTX, Free text C 9 | ---- -----------------------------------------------------------+ --- Segment Group 12 ------------------------ C 9999 -------+ CDS, Code set identification M 1 | FTX, Free text C 9 | | --- Segment Group 13 ------------------------ C 9999 ------+| CDV, Code value definition M 1 || ATT, Attribute C 9 || FTX, Free text C 9 || ---- ----------------------------------------------------------++ UNT, Message trailer M 1