MEDPID Person identification

TBG10 Healthcare

The 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.

Send feedback Share via email

Header

Position
Segment
Name
Max use

  1. A 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: Data element 0065 MEDPID 0052 D 0054 17A 0051 UN

    1. Data element S009/0057 is retained for upward compatibility. The use of
    S016 and/or S017 is encouraged in preference.
    2. The combination of the values carried in data elements 0062 and S009 shall
    be used to identify uniquely the message within its group (if used) or if
    not used, within its interchange, for the purpose of acknowledgement.

  2. A segment for specifying message name and function.

  3. This segment is used to specify the date and time for generation of the message.

  4. This segment contains references to other related messages or documents concerning the whole message.

  5. This segment is used to transfer textual information concerning the message itself.

  6. Segment group 1
    Repeat 99

    1. A segment identifying name and identification of a communication party (i.e. sender and receiver), and other parties associated with the message.

    2. A segment to specify the addresses of the actual communication party.

    3. A segment identifying a contact person or department for the actual communication party to whom communication should be directed.

    4. A segment identifying communication type(s) and number(s) of the actual communication party or contact person or department.

    5. A segment specifying other identification numbers of the actual communication party.

    6. A segment specifying languages used by the actual communication party.

  7. Segment group 2
    Repeat 9999

    1. The 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.

    2. A segment identifying a person.

    3. A segment specifying the addresses of the actual person. One person may have more addresses.

    4. A segment to specify alternate identification numbers of the actual person.

    5. A 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).

    6. A segment for specifying person inherited characteristics such as ethnic origin, hair colour, etc. of the actual person.

    7. A segment for specifying the nationality of the actual person.

    8. A segment for free text information concerning the actual person such as further unstructured person information.

    9. A segment for specifying the languages used by the actual person.

    10. A segment for specifying confidentiality constraints concerning the data of the actual person.

    11. A segment specifying place of birth and/or death of the actual person.

    12. A segment identifying the financial institution(s) and bank account number(s) associated with the actual person.

    13. A segment identifying a person that serves as a contact for the actual person.

    14. Segment group 3
      Repeat 9

      1. A segment to specify the sex, marital status and religion of the actual person.

      2. A segment for specifying the valid date/time/period for the person demographic information.

    15. Segment group 4
      Repeat 9

      1. A segment identifying communication type(s) and number(s) of the actual person.

      2. A segment identifying a contact person or department at the specified communication number.

    16. Segment group 5
      Repeat 99

      1. A segment identifying the type of relationship of the related person or name to the actual person.

      2. A segment identifying the related person or specifying related name(s).

      3. A segment for specifying address information of the related person.

      4. A segment identifying additional identification numbers of the related person.

      5. A segment identifying the time of birth and/or death of the related person.

      6. A segment to specify the sex, marital status and religion of the related person.

      7. A segment for specifying person inherited characteristics such as ethnic origin, hair colour, etc. of the related person.

      8. A segment for specifying the nationality of the related person.

      9. A segment for specifying the languages used by the related person.

  8. Segment group 6
    Repeat 9

    1. A segment specifying details of any authentication (validation) procedure applied to the message.

    2. A segment for specifying the date/time of an authentication procedure.

  9. A 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.

Stedi.comDocumentationContact us

Stedi is a registered trademark of Stedi, Inc. Stedi's EDI Reference is provided for marketing purposes and is free of charge. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.