Return to Stylus Studio EDIFACT home page. Return to Stylus Studio EDIFACT D01C Messages page. Person identification message
0. INTRODUCTIONThis specification provides the definition of the Person identification message (MEDPID) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport. 1. SCOPE1.1. Functional definitionThe message is used to pass detailed information on persons from, for instance, health insurance agencies to local government in order to verify, add, change or delete person related data in information systems. The message may also be used to transfer person information between various application systems within one organisation (i.e. hospital). Usually detailed person related information for one or more persons is sent from one organisation to another who will acknowledge the message that is sent and proceed with changing, adding or deleting person data in their own files or use the transferred information to check their own registers and send a verification message back. 1.2. Field of applicationThe Person identification message may be used for both national and international applications. It is based on universal practice related to administration, commerce and transport, and is not dependent on the type of business or industry. This message may be applied for transfer of person related data between organisations that operate on local, regional, national and/or international level. These organisations typically operate in the field of healthcare, health insurance, government and public affairs. 1.3. PrinciplesDetailed person information may be transferred for more than one person. For each person additional information about related persons and related names may be included. The message may indicate the action that should be taken by the receiving party either to add, change, delete or verify the person information. 2. REFERENCESSee UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 1. 3. TERMS AND DEFINITIONS3.1. Standard terms and definitionsSee UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 2. 4. MESSAGE DEFINITION4.1. Segment clarificationThis section should be read in conjunction with the segment table which indicates mandatory, conditional and repeating requirements. 0010 UNH, Message headerA service segment starting and uniquely identifying a message. The message type code for the Person identification message is MEDPID. Note: Person identification messages conforming to this document must contain the following data in segment UNH, composite S009:
0020 BGM, Beginning of messageA segment for specifying message name and function. 0030 DTM, Date/time/periodThis segment is used to specify the date and time for generation of the message. 0040 RFF, ReferenceThis segment contains references to other related messages or documents concerning the whole message. 0050 FTX, Free textThis segment is used to transfer textual information concerning the message itself. 0060 Segment Group 1: PNA-ADR-CTA-COM-RFF-LANThis segment group is used to transfer information about the parties involved in the actual data interchange. Also information about parties to receive copies may be specified. 0070 PNA, Party identificationA segment identifying name and identification of a communication party (i.e. sender and receiver), and other parties associated with the message. 0080 ADR, AddressA segment to specify the addresses of the actual communication party. 0090 CTA, Contact informationA segment identifying a contact person or department for the actual communication party to whom communication should be directed. 0100 COM, Communication contactA segment identifying communication type(s) and number(s) of the actual communication party or contact person or department. 0110 RFF, ReferenceA segment specifying other identification numbers of the actual communication party. 0120 LAN, LanguageA segment specifying languages used by the actual communication party. 0130 Segment Group 2: GIS-PNA-ADR-RFF-DTM-IHC-NAT-FTX-LAN-HAN-LOC-FII-CTA-SG3-SG4-SG5 This segment group contains information about a person. 0140 X GIS, General indicatorThe segment is used to specify the type of data transferred and the subsequent action assumed to be taken by the receiver such as: - new data to be added (i.e. birth) - old data to be deleted (i.e. death) - modified data (i.e. marriage, address changes) - data to be verified. 0150 PNA, Party identificationA segment identifying a person. 0160 ADR, AddressA segment specifying the addresses of the actual person. One person may have more addresses. 0170 RFF, ReferenceA segment to specify alternate identification numbers of the actual person. 0180 DTM, Date/time/periodA segment identifying the date and time of birth and/or death of the actual person as well as the date to perform the requested action (add, delete, change, verify). 0190 IHC, Person characteristicA segment for specifying person inherited characteristics such as ethnic origin, hair colour, etc. of the actual person. 0200 NAT, NationalityA segment for specifying the nationality of the actual person. 0210 FTX, Free textA segment for free text information concerning the actual person such as further unstructured person information. 0220 LAN, LanguageA segment for specifying the languages used by the actual person. 0230 HAN, Handling instructionsA segment for specifying confidentiality constraints concerning the data of the actual person. 0240 LOC, Place/location identificationA segment specifying place of birth and/or death of the actual person. 0250 FII, Financial institution informationA segment identifying the financial institution(s) and bank account number(s) associated with the actual person. 0260 CTA, Contact informationA segment identifying a person that serves as a contact for the actual person. 0270 Segment Group 3: PDI-DTMA segment group for specifying person demographic information valid at a specific date/time/period. 0280 PDI, Person demographic informationA segment to specify the sex, marital status and religion of the actual person. 0290 DTM, Date/time/periodA segment for specifying the valid date/time/period for the person demographic information. 0300 Segment Group 4: COM-CTAA segment group for specifying communication numbers and contacts of the actual person. 0310 COM, Communication contactA segment identifying communication type(s) and number(s) of the actual person. 0320 CTA, Contact informationA segment identifying a contact person or department at the specified communication number. 0330 Segment Group 5: REL-PNA-ADR-RFF-DTM-PDI-IHC-NAT-LANA segment group identifying any related person or additional names of the actual person. 0340 REL, RelationshipA segment identifying the type of relationship of the related person or name to the actual person. 0350 PNA, Party identificationA segment identifying the related person or specifying related name(s). 0360 ADR, AddressA segment for specifying address information of the related person. 0370 RFF, ReferenceA segment identifying additional identification numbers of the related person. 0380 DTM, Date/time/periodA segment identifying the time of birth and/or death of the related person. 0390 PDI, Person demographic informationA segment to specify the sex, marital status and religion of the related person. 0400 IHC, Person characteristicA segment for specifying person inherited characteristics such as ethnic origin, hair colour, etc. of the related person. 0410 NAT, NationalityA segment for specifying the nationality of the related person. 0420 LAN, LanguageA segment for specifying the languages used by the related person. 0430 Segment Group 6: AUT-DTMA segment group specifying the authentication procedure applied. 0440 AUT, Authentication resultA segment specifying details of any authentication (validation) procedure applied to the message. 0450 DTM, Date/time/periodA segment for specifying the date/time of an authentication procedure. 0460 UNT, 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. 4.2. Segment index (alphabetical sequence by tag)
4.3. Message structure4.3.1. Segment table
Return to Stylus Studio EDIFACT D01C Messages page. |
Site Map | Privacy Policy | Terms of Use | Trademarks |