In de laboratoriumwereld is uitbesteden van werk aan de orde van de dag. Geen enkel laboratorium kan iedere aangevraagde test zelf uitvoeren. Wanneer werk wordt uitbesteed, gebeurt dat middels een labaanvraagbericht, dat in de regel wordt verstuurd met het materiaal. Het uitvoerend laboratorium verstuurt als gevolg van de aanvraag uiteindelijk een labresultaatbericht. Het proces is verdeeld in een aanvraagstroom en een resultaatstroom. De exacte invulling van de aanvraagstroom en de resultaatstroom kan op basis van lokale afspraken worden ingevuld. De minimale invulling van het proces is één aanvraag, gevolgd door één resultaat. Zie de beschrijving van aanvraag- en resultaatstroom voor meer details. Deze applicatierol besteedt laboratoriumresultaten uit aan een ander laboratorium Deze applicatierol neemt uitbesteedde laboratoriumresultaten aan van een ander laboratorium ER7 Het MSH-segment definieert intentie, bron, doel en enkele specifieke dingen rondom de berichtsyntax. Dit veld bevat het scheidingsteken tussen het segment-ID en het eerste echte veld, MSH-2-encoding characters. Deze dient als zodanig als scheidingsteken en definieert het teken dat moet worden gebruikt als scheidingsteken voor het verdere bericht. Aanbevolen waarde is |, (ASCII 124). Dit veld bevat vier tekens in de volgende volgorde: Het componentscheidingsteken, herhalingsteken, escape-teken en subcomponentscheidingsteken. Aanbevolen zijn ^~\& (respectievelijk ASCII 94, 126, 92 en 38). Zie Sectie 2.5.4, "Message delimiters'. Identificatie van het zendende systeem. Voor laboratoria wordt dit geacht de Nederlandse, driecijferige laboratoriumcode te zijn. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Dit veld definieert de zendende applicatie nader, MSH-3-sending application. Met de promotie van dit veld naar het datatype HD, is het gebruik verbreed met niet alleen de zendende instelling maar ook andere organisatorische eenheden zoals a) de organisatorische eenheid verantwoordelijk voor de zendende applicatie; b) de verantwordelijke eenheid; c) een product- of levernaciersidentificatie, etc. De waarden worden lokaal bepaald. User-defined Table 0362 - Facility wordt gebruikt voor de waarden van het eerste component.NB: Afhankelijk van lokale afspraken, kunnen implementers User-defined Table 0300 – Namespace ID blijven gebruiken voor het eerste component. Vullen indien bekend User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Identificatie van het ontvangende systeem. Voor laboratoria wordt dit geacht de Nederlandse, driecijferige laboratoriumcode te zijn. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Dit veld definieert de ontvangende applicatie nader tussen diverse instanties van de applicatie ten behoeve van verschillende organisaties. De waarden worden lokaal bepaald. User-defined Table 0362 - Facility wordt gebruikt voor de waarden van het eerste component.NB: Afhankelijk van lokale afspraken, kunnen implementers User-defined Table 0300 – Namespace ID blijven gebruiken voor het eerste component. Vullen indien bekend User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Dit veld bevat de datum/tijd dat het zendende systeem het bericht heeft gemaakt. Als de tijdzone is opgegeven, dan wordt deze gebruikt als standaardtijdzone voor de rest van het bericht.NB: Dit veld is required gemaakt in versie 2.4. Berichten met versies voor 2.4 hoeven dit veld niet gebruiken. Dit ondersteunt backward compatibiliteit. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| In sommige toepassingen van HL7 wordt dit veld gebruikt voor implementatie van beveiliging/veiligheidsfunctionaliteit. Het gebruik wordt niet nader toegelicht. Dit veld bevat het berichttype (zoals OML, ORL, OOUL, ACK), trigger event (bij een ACK is dat een kopie van de trigger uit het inkomend bericht) en berichtstructuur (zoals OML_OO21, ORL_O22, OUL_R22 of ACK) voor het bericht. Specifies the message type code. Refer to HL7 Table – Message Type in section 2.17.1 for valid values. This table contains values such as ACK, ADT, ORM, ORU etc. See section 2.5.1- Messages for further discussion. Specifies the trigger event code. Refer to HL7 Table – Event Type in section 2.17.2 for valid values. This table contains values like A01, O01, R01 etc. See section 2.3.1 – Trigger Events for further discussion. Specifies the abstract message structure code. Refer to HL7 Table 0354 – Message Structure in section 2.17.3 for valid values. Dit veld bevat een getal of andere identificatie die het bericht uniek identificeert. Het ontvangende systeem echoot dit ID aan het zenden systeem in het Message acknowledgment segment (MSA). Dit veld wordt gebruikt om te beslissen of het bericht moet worden verwerkt volgens de HL7 Application (level 7) Processing rules. Tijdens de pilot: TTijdens productie: P A value that defines whether the message is part of a production, training, or debugging system. Refer to HL7 Table 0103 - Processing ID for valid values. A value that defines whether the message is part of an archival process or an initial load. Refer to HL7 Table 0207 - Processing mode for valid values. Berichtversie. In de component <internationalization code> kan de drieletterige ISO-3166 landcode 'NLD' gezet worden om aan te geven dat het gaat om de Nederlandse variant. Used to identify the HL7 version. Refer to HL7 Table 0104 – Version ID in section 2.15.9.12 for valid values. Used to identify the international affiliate country code. The values to be used are those of ISO 3166 -1:1977. The ISO 3166 table has three separate forms of the country code: HL7 specifies that the 3-character (alphabetic) form be used for the country code. Refer to HL7 Table 0399 – Country code in section 2.15.9.17 for the 3-character codes as defined by ISO 3166 table. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. This field component identifies international affiliate’s version; it is especially important when the international affiliate has more than a single local version associated with a single US version. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Een niet-null waarde in dit veld implicieert dat het sequence number protocol wordt gebruikt. Dit numerieke veld wordt bij iedere volgende waarde verhoogd. - Dit veld biedt de condities waaronder een technische acknowledgement (communicatieniveau) wordt verwacht op dit bericht. Als de zender deze verwacht te krijgen, dan moet hier "AL" worden gestuurd. Als de zender deze niet verwacht te krijgen, dan moet hier "NE" worden gestuurd. Bij een ACK blijft dit veld leeg of is deze null (""). NB: Als MSH-15-accept acknowledgment type en MSH-16-application acknowledgment type worden leeggelaten (oof beide null zijn), dan zijn de original acknowledgment mode regels van toepassing (geen ACK, wel inhoudelijk antwoord zoals ORL). Laat leeg bij original mode acknowledgement (altijd applicatieniveau). Geef een waarde voor enhanced mode acknowledgment (communicatieniveau en/of applicatieniveau) Dit veld biedt de condities waaronder een inhoudelijk acknowledgement (applicatieniveau) wordt verwacht op dit bericht. Als de zender deze verwacht te krijgen, dan moet hier "AL" worden gestuurd. Als de zender deze niet verwacht te krijgen, dan moet hier "NE" worden gestuurd. Bij een ACK blijft dit veld leeg of is deze null (""). NB: Als MSH-15-accept acknowledgment type en MSH-16-application acknowledgment type worden leeggelaten (oof beide null zijn), dan zijn de original acknowledgment mode regels van toepassing (geen ACK, wel inhoudelijk antwoord zoals ORL). Laat leeg bij original mode acknowledgement (altijd applicatieniveau). Geef een waarde voor enhanced mode acknowledgment (communicatieniveau en/of applicatieniveau) Dit veld bevat het land van oorsprong voor het bericht. Het gebruik is voor ten behoeve van het instellen van bepaalde standaardwaarden zoals munteenheden. De waarden komen uit ISO 3166. De tabel ISO 3166 heeft drie vormen voor de landcode: HL7 specificeert gebruik van de 3-teken (alphabetic) vorm voor de landcode.Zie HL7 Table 0399 – Country code voor de 3-teken codes uit ISO 3166-1. Nederland is NLD De standaardwaarde bij afwezigheid is 7-bit ASCII. De meeste systemen zullen de waarde hier negeren en zelf proberen te verwerken. Dat blijkt vrijwel altijd goed te gaan, maar het is toch beter expliciet te zijn in ten aanzien van de gebruikte tekenset. Suggestie is "UNICODE UTF-8" (zonder quotes, deze is nieuw HL7v2.5 en hoger ter vervanging van "UNICODE"). Merk op dat de tekensetcode natuurlijk wel moet kloppen met de gebruikte tekenset. Dit veld bevat de hoofdtaal van het bericht. Normaal is dat Nederlands. Codes komen uit ISO 639. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Als alternatieve tekensets worden gebruikt (zoals gespecificeerd in de tweede of latere herhaling van MSH-18 character sets) en als er speciale verwerking van tekens vereist is, dan dient dit component om deze verwerking te duiden, volgens HL7 Table 0356- Alternate character set handling scheme Het Conformance Profile ID is verplicht en komt overeen met de Template ID voor het betreffende bericht. Er is in principe maar één Conformance Profile ID voorzien, maar het is voorstelbaar dat bij bewezen compatibiliteit met IHE profielen, systemen ook deze markering toevoegen. The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Berichten die voor volksgezondheidsdoeleinden naar RIVM worden gestuurd, moeten worden worden geanonimiseerd. De plaats waar deze anonimisatie van vooral PID-3 en PID-5 plaatsvindt, bij de zender of door een Trusted Third Party (TTP) tussen zender en het RIVM is op basis van lokale afspraken. In berichten die geanonimiseerd dienen te worden/zijn, dienen PID-12 en hoger om privacyredenen geen waarde te bevatten. De normale verwachting is dat het PID-segment terugkomt zoals het is ingestuurd. Na anonimisatie kan dat niet, omdat deze niet omkeerbaar is. Alhoewel het denkbaar is dat in berichten die teruggaan naar de aanvrager, zoals een ORL of een OUL, dan de geanonimiseerde versie van het PID-segment terugkomt, is hiervoor niet gekozen. De verwachting bij dit type berichten is dan ook dat ontvangers matchen op ordernummers/materiaalnummers en niet op PID-gegevens. Het PID-segment met velden PID-3 Patient Identifier List en PID-5 Patient Name, is echter wel verplicht in het bericht. Zie het voorbeeld "minimale vulling in retourberichten", voor hoe het PID-segment er in berichten aan de aanvrager uit dient te zien wanneer een echo van het segment uit de aanvraag niet mogelijk is. Set ID. Dit veld bevat het nummer dat dit segment identificeert binnen het bericht. Bij de eerste keer dat het segment voorkomt, moet het volgnummer 1 zijn, bij de tweede keer is het 2, enzovoorts. Patient ID The value of the identifier itself. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. The algorithm for calculating a Mod10 check digit is as follows: Assume you have an identifier - 12345. Take the odd digit positions, counting from the right, i.e., 531, multiply this number by 2 to get 1062. Take the even digit positions, starting from the right (i.e., 42), prepend these to the 1062 to get 421062. Add all of these six digits together to get 15. Subtract this number from the next highest multiple of 10, i.e., 20 - 15 to get 5. The Mod10 check digit is 5. The Mod10 check digit for 401 is 0; for 9999, it’s 4; for 99999999, it’s 8. The algorithm for calculating a Mod11 check digit is as follows: Terms d = digit of number starting from units digit, followed by 10’s position, followed by 100’s position, etc. w = weight of digit position starting with the units position, followed by 10’s position, followed by 100’s position etc. Values for w = 2, 3, 4, 5, 6, 7, 2, 3, 4, 5, 6, 7, etc. (repeats for each group of 6 digits) c = check digit Calculation (Step 1) m = sum of (d * w) for positions 1, 2, etc. starting with units digit for d = digit value starting with units position to highest order for w = weight value from 2 to 7 for every six positions starting with units digit (Step 2) c1 = m mod 11 (Step 3) if c1 = 0 then reset c1 = 1 (Step 4) = (11 - c1) mod 10 Example: If the number is 1234567, then the mod 11 check digit = 4 The calculations are: M = (7*2)+(6*3)+(5*4)+(4*5)+(3*6)+(2*7)+(1*2) = 14 + 18 + 20 + 20 + 18 + 14 + 2 = 106 c1 = 106 mod 11 = 7 c = (11-c1) mod 10 = 4 mod 10 = 4 Other variants of these check digit algorithms exist and may be used by local bilateral site agreement. Note: The check digit and code identifying check digit scheme are null if ID is alphanumeric. The assigning authority is a unique name of the system (or organization or agency or department) that creates the data. . Refer to User-defined Table 0363 – Assigning authority for suggested values. The reader is referred to the CX.9 and the CX.10 if there is a need to transmit values with semantic meaning for an assigning jurisdiction or assigning department or agency in addition to, or instead of, an assigning authority. However, all 3 components may be valued. If, in so doing, it is discovered that the values in CX.9 and/or CX.10 conflict with CX.4, the user would look to the Message Profile or other implementation agreement for a statement as to which takes precedence. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the patient. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component), may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The first date, if known, on which the identifier is valid and active. The last date, if known, on which the identifier is valid and active. The geo-political body that assigned the identifier in component 1. Refer to HL7 Table 0399 Country Code in section 2.15.9.17 for valid values if the administrative unit under whose jurisdiction the identifier was issued is a country. Refer to User-Defined Table 0347 State/Province for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a state or province. This table is country specific. In the US postal codes may be used. Refer to User-defined Table –0289 County/Parish for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a county or parish. The reader is referred to the CX.4, if there is a need to transmit this information as an OID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. Refer to User-defined Table –0530 Organizations, Agency, Department for suggested values if the administrative unit under whose jurisdiction the identifier was issued is an organization, agency or department. This is populated with site-specific assigning authorities. It also should contain national or international codes when CX-5 Identifier Type may be assigned by more than one authority within a governmental or organizational unit. For example, a federal government may have 2 departments that assign a military identifier, its Veterans Affairs department and its department of defense. It is not recommended to include values for entities such as Social Security Administration (SSA), Immigration and Naturalization Service (INS), Center for Medicare and Medicaid Services (CMS) because they are included in the identifier type table. In these cases the name of the country plus the identifier type yields the correct interpretation of the identifier in component one. Likewise, entries like department of motor vehicles (DMV) and licensing boards are not recommended for inclusion because the combination of state and identifier type yields the correct interpretation of the identifier in component one. This approach is not to be confused with the detailed information provided in the chapter 15 segments that have provision for specifying the precise granting body and issuing body information needed in personnel management messages. Example 1: <Identifier> plus <Visa> yields a unique identifier. Example 2: <Identifier> plus <state> plus <DLN> yields a unique driver’s license number. Example 3: <Identifier> plus <country> plus <INS> yields a unique immigration number. The reader is referred to the CX.4, if there is a need to transmit this information as an OID. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Lijst van patiëntidentificaties. Er worden maximaal slechts twee typen identificatie ondersteund in dit herhalende veld: het burgerservicenummer en het interne patiëntnummer zoals bekend bij de aanvrager. Aanname is dat als het burgerservicenummer ontbreekt in het bericht, deze dan bij aanvragen niet bekend, of niet geverifieerd was.In het geval van anonimisatie bevat het eerste subveld na anonimisatie de uitkomst van het algoritme, het vierde subveld de Assigning authority en het vijfde subveld Identifier type code de vaste waarde "ANON-" (Anonymous identifier) + de oorspronkelijke waarde vóór anonimisatie. The value of the identifier itself. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. The algorithm for calculating a Mod10 check digit is as follows: Assume you have an identifier - 12345. Take the odd digit positions, counting from the right, i.e., 531, multiply this number by 2 to get 1062. Take the even digit positions, starting from the right (i.e., 42), prepend these to the 1062 to get 421062. Add all of these six digits together to get 15. Subtract this number from the next highest multiple of 10, i.e., 20 - 15 to get 5. The Mod10 check digit is 5. The Mod10 check digit for 401 is 0; for 9999, it’s 4; for 99999999, it’s 8. The algorithm for calculating a Mod11 check digit is as follows: Terms d = digit of number starting from units digit, followed by 10’s position, followed by 100’s position, etc. w = weight of digit position starting with the units position, followed by 10’s position, followed by 100’s position etc. Values for w = 2, 3, 4, 5, 6, 7, 2, 3, 4, 5, 6, 7, etc. (repeats for each group of 6 digits) c = check digit Calculation (Step 1) m = sum of (d * w) for positions 1, 2, etc. starting with units digit for d = digit value starting with units position to highest order for w = weight value from 2 to 7 for every six positions starting with units digit (Step 2) c1 = m mod 11 (Step 3) if c1 = 0 then reset c1 = 1 (Step 4) = (11 - c1) mod 10 Example: If the number is 1234567, then the mod 11 check digit = 4 The calculations are: M = (7*2)+(6*3)+(5*4)+(4*5)+(3*6)+(2*7)+(1*2) = 14 + 18 + 20 + 20 + 18 + 14 + 2 = 106 c1 = 106 mod 11 = 7 c = (11-c1) mod 10 = 4 mod 10 = 4 Other variants of these check digit algorithms exist and may be used by local bilateral site agreement. Note: The check digit and code identifying check digit scheme are null if ID is alphanumeric. The assigning authority is a unique name of the system (or organization or agency or department) that creates the data. . Refer to User-defined Table 0363 – Assigning authority for suggested values. The reader is referred to the CX.9 and the CX.10 if there is a need to transmit values with semantic meaning for an assigning jurisdiction or assigning department or agency in addition to, or instead of, an assigning authority. However, all 3 components may be valued. If, in so doing, it is discovered that the values in CX.9 and/or CX.10 conflict with CX.4, the user would look to the Message Profile or other implementation agreement for a statement as to which takes precedence. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the patient. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component), may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The first date, if known, on which the identifier is valid and active. The last date, if known, on which the identifier is valid and active. The geo-political body that assigned the identifier in component 1. Refer to HL7 Table 0399 Country Code in section 2.15.9.17 for valid values if the administrative unit under whose jurisdiction the identifier was issued is a country. Refer to User-Defined Table 0347 State/Province for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a state or province. This table is country specific. In the US postal codes may be used. Refer to User-defined Table –0289 County/Parish for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a county or parish. The reader is referred to the CX.4, if there is a need to transmit this information as an OID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. Refer to User-defined Table –0530 Organizations, Agency, Department for suggested values if the administrative unit under whose jurisdiction the identifier was issued is an organization, agency or department. This is populated with site-specific assigning authorities. It also should contain national or international codes when CX-5 Identifier Type may be assigned by more than one authority within a governmental or organizational unit. For example, a federal government may have 2 departments that assign a military identifier, its Veterans Affairs department and its department of defense. It is not recommended to include values for entities such as Social Security Administration (SSA), Immigration and Naturalization Service (INS), Center for Medicare and Medicaid Services (CMS) because they are included in the identifier type table. In these cases the name of the country plus the identifier type yields the correct interpretation of the identifier in component one. Likewise, entries like department of motor vehicles (DMV) and licensing boards are not recommended for inclusion because the combination of state and identifier type yields the correct interpretation of the identifier in component one. This approach is not to be confused with the detailed information provided in the chapter 15 segments that have provision for specifying the precise granting body and issuing body information needed in personnel management messages. Example 1: <Identifier> plus <Visa> yields a unique identifier. Example 2: <Identifier> plus <state> plus <DLN> yields a unique driver’s license number. Example 3: <Identifier> plus <country> plus <INS> yields a unique immigration number. The reader is referred to the CX.4, if there is a need to transmit this information as an OID. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Alternate Patient ID - PID The value of the identifier itself. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. The algorithm for calculating a Mod10 check digit is as follows: Assume you have an identifier - 12345. Take the odd digit positions, counting from the right, i.e., 531, multiply this number by 2 to get 1062. Take the even digit positions, starting from the right (i.e., 42), prepend these to the 1062 to get 421062. Add all of these six digits together to get 15. Subtract this number from the next highest multiple of 10, i.e., 20 - 15 to get 5. The Mod10 check digit is 5. The Mod10 check digit for 401 is 0; for 9999, it’s 4; for 99999999, it’s 8. The algorithm for calculating a Mod11 check digit is as follows: Terms d = digit of number starting from units digit, followed by 10’s position, followed by 100’s position, etc. w = weight of digit position starting with the units position, followed by 10’s position, followed by 100’s position etc. Values for w = 2, 3, 4, 5, 6, 7, 2, 3, 4, 5, 6, 7, etc. (repeats for each group of 6 digits) c = check digit Calculation (Step 1) m = sum of (d * w) for positions 1, 2, etc. starting with units digit for d = digit value starting with units position to highest order for w = weight value from 2 to 7 for every six positions starting with units digit (Step 2) c1 = m mod 11 (Step 3) if c1 = 0 then reset c1 = 1 (Step 4) = (11 - c1) mod 10 Example: If the number is 1234567, then the mod 11 check digit = 4 The calculations are: M = (7*2)+(6*3)+(5*4)+(4*5)+(3*6)+(2*7)+(1*2) = 14 + 18 + 20 + 20 + 18 + 14 + 2 = 106 c1 = 106 mod 11 = 7 c = (11-c1) mod 10 = 4 mod 10 = 4 Other variants of these check digit algorithms exist and may be used by local bilateral site agreement. Note: The check digit and code identifying check digit scheme are null if ID is alphanumeric. The assigning authority is a unique name of the system (or organization or agency or department) that creates the data. . Refer to User-defined Table 0363 – Assigning authority for suggested values. The reader is referred to the CX.9 and the CX.10 if there is a need to transmit values with semantic meaning for an assigning jurisdiction or assigning department or agency in addition to, or instead of, an assigning authority. However, all 3 components may be valued. If, in so doing, it is discovered that the values in CX.9 and/or CX.10 conflict with CX.4, the user would look to the Message Profile or other implementation agreement for a statement as to which takes precedence. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the patient. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component), may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The first date, if known, on which the identifier is valid and active. The last date, if known, on which the identifier is valid and active. The geo-political body that assigned the identifier in component 1. Refer to HL7 Table 0399 Country Code in section 2.15.9.17 for valid values if the administrative unit under whose jurisdiction the identifier was issued is a country. Refer to User-Defined Table 0347 State/Province for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a state or province. This table is country specific. In the US postal codes may be used. Refer to User-defined Table –0289 County/Parish for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a county or parish. The reader is referred to the CX.4, if there is a need to transmit this information as an OID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. Refer to User-defined Table –0530 Organizations, Agency, Department for suggested values if the administrative unit under whose jurisdiction the identifier was issued is an organization, agency or department. This is populated with site-specific assigning authorities. It also should contain national or international codes when CX-5 Identifier Type may be assigned by more than one authority within a governmental or organizational unit. For example, a federal government may have 2 departments that assign a military identifier, its Veterans Affairs department and its department of defense. It is not recommended to include values for entities such as Social Security Administration (SSA), Immigration and Naturalization Service (INS), Center for Medicare and Medicaid Services (CMS) because they are included in the identifier type table. In these cases the name of the country plus the identifier type yields the correct interpretation of the identifier in component one. Likewise, entries like department of motor vehicles (DMV) and licensing boards are not recommended for inclusion because the combination of state and identifier type yields the correct interpretation of the identifier in component one. This approach is not to be confused with the detailed information provided in the chapter 15 segments that have provision for specifying the precise granting body and issuing body information needed in personnel management messages. Example 1: <Identifier> plus <Visa> yields a unique identifier. Example 2: <Identifier> plus <state> plus <DLN> yields a unique driver’s license number. Example 3: <Identifier> plus <country> plus <INS> yields a unique immigration number. The reader is referred to the CX.4, if there is a need to transmit this information as an OID. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Patiënt naam. In HL7 een verplicht veld.Bij anonimisatie worden namen verwijderd of geanonimiseerd. In het XPN-7 component “Name Type Code” kan hier de code S (Coded Pseudo-Name to ensure anonymity) worden gebruikt. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, "FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. This component cannot be fully expressed. Identified as v 2.4 erratum. Retained for backward compatibility only as of v 2.5. Refer to Effective Date and Expiration Date components. This component contains the start and end date/times, which define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 0444 – Name assembly order for valid values. The first date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. Mother's Maiden Name This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, "FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. This component cannot be fully expressed. Identified as v 2.4 erratum. Retained for backward compatibility only as of v 2.5. Refer to Effective Date and Expiration Date components. This component contains the start and end date/times, which define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 0444 – Name assembly order for valid values. The first date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. Geboortedatum.Verplicht voor RIVM. Format JJJJMMDD. Na anonimisatie wordt de waarde beperkt tot JJJJMM. Verplicht in aanvraagberichten. Optioneel of null in aanvraag-antwoorden en resultaatberichten The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Administratief geslacht Verplicht in aanvraagberichten. Optioneel of null in aanvraag-antwoorden en resultaatberichten Patient Alias This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, "FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. This component cannot be fully expressed. Identified as v 2.4 erratum. Retained for backward compatibility only as of v 2.5. Refer to Effective Date and Expiration Date components. This component contains the start and end date/times, which define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 0444 – Name assembly order for valid values. The first date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. Race Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Patiëntadres.Bij anonimisatie wordt het adres beperkt tot de vier cijfers van de postcode en het land. Voor buitenlandse adressen kan de postcode bij anonimisatie volledig worden verwijderd en blijft alleen de landcode staan. Verplicht in aanvraagberichten. Optioneel of null in aanvraag-antwoorden en resultaatberichten Adres straat - Vanaf versie 2.4 is ‘street address’ een samengesteld datatype, waar in de verschillende onderdelen van het adres in verschillende subcomponenten kunnen worden opgenomen This component specifies the street or mailing address of a person or institution. When referencing an institution, this first component is used to specify the institution name. When used in connection with a person, this component specifies the first line of the address. Street Name Dwelling Number Huisnummertoevoeging Woonplaats Staat of provincie. Meestal niet relevant, maar gebruiken bij plaatsnamen in meerdere provincies zoals Afferden (Gelderland en Limburg) en Bergen (Noord-Holland en Limburg) Postcode, indien een Nederlandse postcode dan zonder spaties dus bijv. 2316XA. Merk op dat de HL7v3 specificatie met een spatie voorschrijft. Er is hier bewust gekozen voor compatibiliteit met de officiële HL7v2.4 NL specificatie. Land Adrestype. Voor het eerste adres moet deze de waarde ‘M’ (mailing) hebben. Andere adressen kunnen ook worden doorgegeven, zoals bijv. huisadres (‘H’), of tijdelijk/verblijfsadres (‘C’). Andere geografische aanduiding. N.v.t. voor Nederlandse adressen County/graafschap code. N.v.t. voor Nederlandse adressen Census tract. N.v.t. voor Nederlandse adressen. Representatiecode adres. N.v.t. voor Nederlandse adressen Adres geldigheidsperiode. Hierin kunnen eventueel de begin- en einddatum worden doorgegeven waarbinnen een adres geldig is. Dit kan bijv. voor tijdelijke adressen relevant zijn. Het is echter gemarkeerd als obsoleet en behouden voor backward compatbility in versie 2.5. Zie in plaats daarvan XAD.13 en XAD.14. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. Geldigheidsdatum. De eerste datum, indien bekend, waarop het adres geldig is/was en actief. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Verloopdatum. De laatste datum, indien bekend, waarop het adres geldig is/was en actief. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| County Code Telefoonnummer - Privé. Dit veld bevat alle telefoonnummers van de patiënt. Het eerste telefoonnummer moet het primaire nummer van de patiënt zijn. (Telecommunication use code ‘PRN’). Als het primaire telefoonnummer niet bekend is, moet een ‘repetition delimiter’ worden gestuurd, voorafgaand aan het eerste telefoonnummer. Merk op dat een mobiel nummer ook een ‘Primary Residence Number’ kan zijn. Specifies the telephone number in a predetermined format that includes an optional extension, beeper number and comment. This component has been retained for backward compatibility only as of version 2.3. Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C any text] Note: Because this component has been deprecated a new data type has not been defined to replace the formatted ST. A code that represents a specific use of a telecommunication number. Refer to HL7 Table 0201 - Telecommunication use code for valid values. A code that represents the type of telecommunication equipment. Refer to HL7 Table 0202 - Telecommunication equipment type for valid values. Internationalization note: To make this data type interoperate with CEN’s Telecommunication data attribute group, we allow use of the second component for email addresses. The presence of an email address is specified by the addition of the value NET to the Phone Use Code table, and the type of Internet address is specified with the values Internet and X.400 to the Phone Equipment Type table. When used for an Internet address, the first component of the XTN data type will be null. If the @-sign is being used as a subcomponent delimiter, the HL7 subcomponent escape sequence may be used when encoding an Internet address (see Section Country Code (NM). Country Code Area/City Code Local Number Extension Contains comments with respect to the telephone number. The characters established within a company’s internal telephone system network used as a prefix to the Extension component for internal dialing. Note that the use of Extension Prefix requires that the Extension component be valued and that digits, as well as special characters (e.g., *, #) may be used. The characters established within a company’s internal telephone system used in place of the (external) telephone number to facilitate calling because its length is shorter than that of the telephone number. Note that digits, as well as special characters (e.g., *, #) may be used. An expression of the telephone number as an unparsible string. The phone number was entered as free text and sending system does not know how to parse it. Telefoonnummer - Zakelijk Specifies the telephone number in a predetermined format that includes an optional extension, beeper number and comment. This component has been retained for backward compatibility only as of version 2.3. Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C any text] Note: Because this component has been deprecated a new data type has not been defined to replace the formatted ST. A code that represents a specific use of a telecommunication number. Refer to HL7 Table 0201 - Telecommunication use code for valid values. A code that represents the type of telecommunication equipment. Refer to HL7 Table 0202 - Telecommunication equipment type for valid values. Internationalization note: To make this data type interoperate with CEN’s Telecommunication data attribute group, we allow use of the second component for email addresses. The presence of an email address is specified by the addition of the value NET to the Phone Use Code table, and the type of Internet address is specified with the values Internet and X.400 to the Phone Equipment Type table. When used for an Internet address, the first component of the XTN data type will be null. If the @-sign is being used as a subcomponent delimiter, the HL7 subcomponent escape sequence may be used when encoding an Internet address (see Section Country Code (NM). Country Code Area/City Code Local Number Extension Contains comments with respect to the telephone number. The characters established within a company’s internal telephone system network used as a prefix to the Extension component for internal dialing. Note that the use of Extension Prefix requires that the Extension component be valued and that digits, as well as special characters (e.g., *, #) may be used. The characters established within a company’s internal telephone system used in place of the (external) telephone number to facilitate calling because its length is shorter than that of the telephone number. Note that digits, as well as special characters (e.g., *, #) may be used. An expression of the telephone number as an unparsible string. The phone number was entered as free text and sending system does not know how to parse it. Primary Language Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Burgerlijke staat Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Religion Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Patient Account Number The value of the identifier itself. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. The algorithm for calculating a Mod10 check digit is as follows: Assume you have an identifier - 12345. Take the odd digit positions, counting from the right, i.e., 531, multiply this number by 2 to get 1062. Take the even digit positions, starting from the right (i.e., 42), prepend these to the 1062 to get 421062. Add all of these six digits together to get 15. Subtract this number from the next highest multiple of 10, i.e., 20 - 15 to get 5. The Mod10 check digit is 5. The Mod10 check digit for 401 is 0; for 9999, it’s 4; for 99999999, it’s 8. The algorithm for calculating a Mod11 check digit is as follows: Terms d = digit of number starting from units digit, followed by 10’s position, followed by 100’s position, etc. w = weight of digit position starting with the units position, followed by 10’s position, followed by 100’s position etc. Values for w = 2, 3, 4, 5, 6, 7, 2, 3, 4, 5, 6, 7, etc. (repeats for each group of 6 digits) c = check digit Calculation (Step 1) m = sum of (d * w) for positions 1, 2, etc. starting with units digit for d = digit value starting with units position to highest order for w = weight value from 2 to 7 for every six positions starting with units digit (Step 2) c1 = m mod 11 (Step 3) if c1 = 0 then reset c1 = 1 (Step 4) = (11 - c1) mod 10 Example: If the number is 1234567, then the mod 11 check digit = 4 The calculations are: M = (7*2)+(6*3)+(5*4)+(4*5)+(3*6)+(2*7)+(1*2) = 14 + 18 + 20 + 20 + 18 + 14 + 2 = 106 c1 = 106 mod 11 = 7 c = (11-c1) mod 10 = 4 mod 10 = 4 Other variants of these check digit algorithms exist and may be used by local bilateral site agreement. Note: The check digit and code identifying check digit scheme are null if ID is alphanumeric. The assigning authority is a unique name of the system (or organization or agency or department) that creates the data. . Refer to User-defined Table 0363 – Assigning authority for suggested values. The reader is referred to the CX.9 and the CX.10 if there is a need to transmit values with semantic meaning for an assigning jurisdiction or assigning department or agency in addition to, or instead of, an assigning authority. However, all 3 components may be valued. If, in so doing, it is discovered that the values in CX.9 and/or CX.10 conflict with CX.4, the user would look to the Message Profile or other implementation agreement for a statement as to which takes precedence. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the patient. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component), may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The first date, if known, on which the identifier is valid and active. The last date, if known, on which the identifier is valid and active. The geo-political body that assigned the identifier in component 1. Refer to HL7 Table 0399 Country Code in section 2.15.9.17 for valid values if the administrative unit under whose jurisdiction the identifier was issued is a country. Refer to User-Defined Table 0347 State/Province for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a state or province. This table is country specific. In the US postal codes may be used. Refer to User-defined Table –0289 County/Parish for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a county or parish. The reader is referred to the CX.4, if there is a need to transmit this information as an OID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. Refer to User-defined Table –0530 Organizations, Agency, Department for suggested values if the administrative unit under whose jurisdiction the identifier was issued is an organization, agency or department. This is populated with site-specific assigning authorities. It also should contain national or international codes when CX-5 Identifier Type may be assigned by more than one authority within a governmental or organizational unit. For example, a federal government may have 2 departments that assign a military identifier, its Veterans Affairs department and its department of defense. It is not recommended to include values for entities such as Social Security Administration (SSA), Immigration and Naturalization Service (INS), Center for Medicare and Medicaid Services (CMS) because they are included in the identifier type table. In these cases the name of the country plus the identifier type yields the correct interpretation of the identifier in component one. Likewise, entries like department of motor vehicles (DMV) and licensing boards are not recommended for inclusion because the combination of state and identifier type yields the correct interpretation of the identifier in component one. This approach is not to be confused with the detailed information provided in the chapter 15 segments that have provision for specifying the precise granting body and issuing body information needed in personnel management messages. Example 1: <Identifier> plus <Visa> yields a unique identifier. Example 2: <Identifier> plus <state> plus <DLN> yields a unique driver’s license number. Example 3: <Identifier> plus <country> plus <INS> yields a unique immigration number. The reader is referred to the CX.4, if there is a need to transmit this information as an OID. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. SSN Number - Patient Driver's License Number - Patient This field contains the driver’s license number. Issuing authority for driver’s license. For state or province refer to official postal codes for that country; for country refer to ISO 3166 for codes. The ISO 3166 table has three separate forms of the country code: HL7 specifies that the 3-character (alphabetic) form be used for the country code. User-defined Table 0333 - Driver’s license issuing authority is used as the HL7 identifier for the user-defined table of values for this component. Expiration date (DT) for driver’s license. Mother's Identifier The value of the identifier itself. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. The algorithm for calculating a Mod10 check digit is as follows: Assume you have an identifier - 12345. Take the odd digit positions, counting from the right, i.e., 531, multiply this number by 2 to get 1062. Take the even digit positions, starting from the right (i.e., 42), prepend these to the 1062 to get 421062. Add all of these six digits together to get 15. Subtract this number from the next highest multiple of 10, i.e., 20 - 15 to get 5. The Mod10 check digit is 5. The Mod10 check digit for 401 is 0; for 9999, it’s 4; for 99999999, it’s 8. The algorithm for calculating a Mod11 check digit is as follows: Terms d = digit of number starting from units digit, followed by 10’s position, followed by 100’s position, etc. w = weight of digit position starting with the units position, followed by 10’s position, followed by 100’s position etc. Values for w = 2, 3, 4, 5, 6, 7, 2, 3, 4, 5, 6, 7, etc. (repeats for each group of 6 digits) c = check digit Calculation (Step 1) m = sum of (d * w) for positions 1, 2, etc. starting with units digit for d = digit value starting with units position to highest order for w = weight value from 2 to 7 for every six positions starting with units digit (Step 2) c1 = m mod 11 (Step 3) if c1 = 0 then reset c1 = 1 (Step 4) = (11 - c1) mod 10 Example: If the number is 1234567, then the mod 11 check digit = 4 The calculations are: M = (7*2)+(6*3)+(5*4)+(4*5)+(3*6)+(2*7)+(1*2) = 14 + 18 + 20 + 20 + 18 + 14 + 2 = 106 c1 = 106 mod 11 = 7 c = (11-c1) mod 10 = 4 mod 10 = 4 Other variants of these check digit algorithms exist and may be used by local bilateral site agreement. Note: The check digit and code identifying check digit scheme are null if ID is alphanumeric. The assigning authority is a unique name of the system (or organization or agency or department) that creates the data. . Refer to User-defined Table 0363 – Assigning authority for suggested values. The reader is referred to the CX.9 and the CX.10 if there is a need to transmit values with semantic meaning for an assigning jurisdiction or assigning department or agency in addition to, or instead of, an assigning authority. However, all 3 components may be valued. If, in so doing, it is discovered that the values in CX.9 and/or CX.10 conflict with CX.4, the user would look to the Message Profile or other implementation agreement for a statement as to which takes precedence. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the patient. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component), may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The first date, if known, on which the identifier is valid and active. The last date, if known, on which the identifier is valid and active. The geo-political body that assigned the identifier in component 1. Refer to HL7 Table 0399 Country Code in section 2.15.9.17 for valid values if the administrative unit under whose jurisdiction the identifier was issued is a country. Refer to User-Defined Table 0347 State/Province for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a state or province. This table is country specific. In the US postal codes may be used. Refer to User-defined Table –0289 County/Parish for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a county or parish. The reader is referred to the CX.4, if there is a need to transmit this information as an OID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. Refer to User-defined Table –0530 Organizations, Agency, Department for suggested values if the administrative unit under whose jurisdiction the identifier was issued is an organization, agency or department. This is populated with site-specific assigning authorities. It also should contain national or international codes when CX-5 Identifier Type may be assigned by more than one authority within a governmental or organizational unit. For example, a federal government may have 2 departments that assign a military identifier, its Veterans Affairs department and its department of defense. It is not recommended to include values for entities such as Social Security Administration (SSA), Immigration and Naturalization Service (INS), Center for Medicare and Medicaid Services (CMS) because they are included in the identifier type table. In these cases the name of the country plus the identifier type yields the correct interpretation of the identifier in component one. Likewise, entries like department of motor vehicles (DMV) and licensing boards are not recommended for inclusion because the combination of state and identifier type yields the correct interpretation of the identifier in component one. This approach is not to be confused with the detailed information provided in the chapter 15 segments that have provision for specifying the precise granting body and issuing body information needed in personnel management messages. Example 1: <Identifier> plus <Visa> yields a unique identifier. Example 2: <Identifier> plus <state> plus <DLN> yields a unique driver’s license number. Example 3: <Identifier> plus <country> plus <INS> yields a unique immigration number. The reader is referred to the CX.4, if there is a need to transmit this information as an OID. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Ethnic Group Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Birth Place Meerlingindicator. "Y" indien deze persoon onderdeel is van een meerling. "N" indien dat niet het geval is. Indien dit veld geen waarde bevat, kan hieruit geen meerlingstatus uit worden afgeleid. Verplicht indien bekend in aanvraagberichten. Optioneel of null in aanvraag-antwoorden en resultaatberichten Birth Order Citizenship Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Veterans Military Status Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Nationality Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Patient Death Date and Time The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Patient Death Indicator Identity Unknown Indicator Identity Reliability Code Last Update Date/Time The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Last Update Facility User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Species Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Breed Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Strain Production Class Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Tribal Citizenship Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Living Dependency Living Arrangement Patient Primary Facility The name of the specified organization. A code that represents the type of name i.e., legal name, display name. Refer to User-defined Table 0204 - Organizational Name Type for suggested values. This component has been retained for backward compatibility only as of v 2.5. It is recommended to use component 10 Organization identifier that accommodates alphanumeric identifiers. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. The check digit scheme codes are defined in HL7 Table 0061 - Check digit scheme. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Assigning authorities are unique across a given HL7 implementation. Refer to User-defined Table 0363 - Assigning Authority for suggested values. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e. even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation code for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component contains the sequence of characters (the code) that uniquely identifies the item being referenced by XON.1 Organization Name. This component replaces XON.3 ID Number as of v 2.5. Note: The check digit and code identifying check digit scheme are null if Organization identifier is alphanumeric. Patient Primary Care Provider Name & ID No. This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Student Indicator Handicap Living Will Code Organ Donor Code Separate Bill Duplicate Patient The value of the identifier itself. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. The algorithm for calculating a Mod10 check digit is as follows: Assume you have an identifier - 12345. Take the odd digit positions, counting from the right, i.e., 531, multiply this number by 2 to get 1062. Take the even digit positions, starting from the right (i.e., 42), prepend these to the 1062 to get 421062. Add all of these six digits together to get 15. Subtract this number from the next highest multiple of 10, i.e., 20 - 15 to get 5. The Mod10 check digit is 5. The Mod10 check digit for 401 is 0; for 9999, it’s 4; for 99999999, it’s 8. The algorithm for calculating a Mod11 check digit is as follows: Terms d = digit of number starting from units digit, followed by 10’s position, followed by 100’s position, etc. w = weight of digit position starting with the units position, followed by 10’s position, followed by 100’s position etc. Values for w = 2, 3, 4, 5, 6, 7, 2, 3, 4, 5, 6, 7, etc. (repeats for each group of 6 digits) c = check digit Calculation (Step 1) m = sum of (d * w) for positions 1, 2, etc. starting with units digit for d = digit value starting with units position to highest order for w = weight value from 2 to 7 for every six positions starting with units digit (Step 2) c1 = m mod 11 (Step 3) if c1 = 0 then reset c1 = 1 (Step 4) = (11 - c1) mod 10 Example: If the number is 1234567, then the mod 11 check digit = 4 The calculations are: M = (7*2)+(6*3)+(5*4)+(4*5)+(3*6)+(2*7)+(1*2) = 14 + 18 + 20 + 20 + 18 + 14 + 2 = 106 c1 = 106 mod 11 = 7 c = (11-c1) mod 10 = 4 mod 10 = 4 Other variants of these check digit algorithms exist and may be used by local bilateral site agreement. Note: The check digit and code identifying check digit scheme are null if ID is alphanumeric. The assigning authority is a unique name of the system (or organization or agency or department) that creates the data. . Refer to User-defined Table 0363 – Assigning authority for suggested values. The reader is referred to the CX.9 and the CX.10 if there is a need to transmit values with semantic meaning for an assigning jurisdiction or assigning department or agency in addition to, or instead of, an assigning authority. However, all 3 components may be valued. If, in so doing, it is discovered that the values in CX.9 and/or CX.10 conflict with CX.4, the user would look to the Message Profile or other implementation agreement for a statement as to which takes precedence. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the patient. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component), may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The first date, if known, on which the identifier is valid and active. The last date, if known, on which the identifier is valid and active. The geo-political body that assigned the identifier in component 1. Refer to HL7 Table 0399 Country Code in section 2.15.9.17 for valid values if the administrative unit under whose jurisdiction the identifier was issued is a country. Refer to User-Defined Table 0347 State/Province for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a state or province. This table is country specific. In the US postal codes may be used. Refer to User-defined Table –0289 County/Parish for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a county or parish. The reader is referred to the CX.4, if there is a need to transmit this information as an OID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. Refer to User-defined Table –0530 Organizations, Agency, Department for suggested values if the administrative unit under whose jurisdiction the identifier was issued is an organization, agency or department. This is populated with site-specific assigning authorities. It also should contain national or international codes when CX-5 Identifier Type may be assigned by more than one authority within a governmental or organizational unit. For example, a federal government may have 2 departments that assign a military identifier, its Veterans Affairs department and its department of defense. It is not recommended to include values for entities such as Social Security Administration (SSA), Immigration and Naturalization Service (INS), Center for Medicare and Medicaid Services (CMS) because they are included in the identifier type table. In these cases the name of the country plus the identifier type yields the correct interpretation of the identifier in component one. Likewise, entries like department of motor vehicles (DMV) and licensing boards are not recommended for inclusion because the combination of state and identifier type yields the correct interpretation of the identifier in component one. This approach is not to be confused with the detailed information provided in the chapter 15 segments that have provision for specifying the precise granting body and issuing body information needed in personnel management messages. Example 1: <Identifier> plus <Visa> yields a unique identifier. Example 2: <Identifier> plus <state> plus <DLN> yields a unique driver’s license number. Example 3: <Identifier> plus <country> plus <INS> yields a unique immigration number. The reader is referred to the CX.4, if there is a need to transmit this information as an OID. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Publicity Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Protection Indicator Protection Indicator Effective Date Place of Worship The name of the specified organization. A code that represents the type of name i.e., legal name, display name. Refer to User-defined Table 0204 - Organizational Name Type for suggested values. This component has been retained for backward compatibility only as of v 2.5. It is recommended to use component 10 Organization identifier that accommodates alphanumeric identifiers. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. The check digit scheme codes are defined in HL7 Table 0061 - Check digit scheme. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Assigning authorities are unique across a given HL7 implementation. Refer to User-defined Table 0363 - Assigning Authority for suggested values. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e. even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation code for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component contains the sequence of characters (the code) that uniquely identifies the item being referenced by XON.1 Organization Name. This component replaces XON.3 ID Number as of v 2.5. Note: The check digit and code identifying check digit scheme are null if Organization identifier is alphanumeric. Advance Directive Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Immunization Registry Status Immunization Registry Status Effective Date Publicity Code Effective Date Military Branch Military Rank/Grade Military Status The NTE segment is defined here for inclusion in messages defined in other chapters. It is commonly used for sending notes and comments.The technical committees define the meaning of the NTE segments within the context of the messages in their chapters. For each NTE, the description in the message attribute table should include an indication of the segment associated with the NTE, for example "Notes and Comments for the PID". Set ID. Dit veld bevat het nummer dat dit segment identificeert binnen het bericht. Bij de eerste keer dat het segment voorkomt, moet het volgnummer 1 zijn, bij de tweede keer is het 2, enzovoorts. Dit veld wordt gebruik om de bron van de opmerking te duiden. Deze tabel kan lokaal worden uitgebreid bij implementatie. Zie HL7 Tabel 0105 - Source of comment voor alle geldige waarden. In de context van Lab2Lab en Lab2PublicHealth zijn met name deze belangrijk: LAncillary (filler) department is source of commentUitvoerende (filler) laboratorium is bron van de opmerkingPOrderer (placer) is source of commentAanvragende (placer) laboratorium is bron van de opmerkingOOther system is source of commentAnder systeem (bijv. de oorspronkelijke aanvrager) is bron van de opmerking Dit veld bevat de opmerkingtekst van dit segment.NB: Sinds v2.2 volgt dit veld datatype FT in plaats van TX. Aangezien er geen verschil is tussen datatype FT zonder aanvullende opmaakcommando's en het datatype TX, is deze wijziging backward compatibel met de voorgaande versies. Dit veld bevat een waarde om het type opmerking dat wordt gestuurd te duiden. Zie User-Defined Table 0364 - Comment Type voor voorgestelde waarden.NB: Er bestaat ook al een veld in het NTE-segment voor identificatie van de Sources of Comment (bijv. ancillary, placer, anders). Sommige systemen moet echter ook andere typen opmerkingen kunnen onderscheiden (bijv., instructies, reden, opmerkingen, etc.). Om die reden kan voor ieder type opmerking een apart NTE-segment worden gebruikt (bijv., instructies op de ene NTE en opmerkingen in een andere NTE).De volgende waarden worden door RIVM Type-Ned onderscheiden in resultaatberichten:PI - PatiëntinstructiesAI - Aanvullende instructiesGI - Algemene instructies1R - Primaire reden2R - Secundaire redenGR - Algemene redenRE - OpmerkingDR - Duplicaat/interactie reden Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Set ID - NK1 Name This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, "FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. This component cannot be fully expressed. Identified as v 2.4 erratum. Retained for backward compatibility only as of v 2.5. Refer to Effective Date and Expiration Date components. This component contains the start and end date/times, which define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 0444 – Name assembly order for valid values. The first date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. Relationship Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Address See section 2.A.67, "SAD – street address" for description of components. This component specifies the street or mailing address of a person or institution. When referencing an institution, this first component is used to specify the institution name. When used in connection with a person, this component specifies the first line of the address. Street Name Dwelling Number Second line of address. In US usage, it qualifies address. Examples: Suite 555 or Fourth Floor. When referencing an institution, this component specifies the street address. This component specifies the city, or district or place where the addressee is located depending upon the national convention for formatting addresses for postal usage. This component specifies the state or province where the addressee is located. State or province should be represented by the official postal service codes for that country. This component specifies the zip or postal code where the addressee is located. Zip or postal codes should be represented by the official codes for that country. In the US, the zip code takes the form 99999[-9999], while the Canadian postal code takes the form A9A9A9, and the Australian Postcode takes the form 9999. This component specifies the country where the addressee is locatedHL7 specifies that the 3-character (alphabetic) form of ISO 3166 be used for the country code. Refer to HL7 Table 0399 – Country code in section 2.15.9.17 for valid values. This component specifies the kind or type of address. Refer to HL7 Table 0190 - Address type for valid values. This component specifies any other geographic designation. It includes county, bioregion, SMSA, etc. A code that represents the county in which the specified address resides. User-defined Table 0289 - County/parish is used as the HL7 identifier for the user-defined table of values for this component. When this component is used to represent the county (or parish), component 8 <other geographic designation> should not duplicate it (i.e., the use of <other geographic designation> to represent the county is allowed only for the purpose of backward compatibility, and should be discouraged in this and future versions of HL7). Allowable values: codes defined by government. A code that represents the census tract in which the specified address resides. User-defined Table 0288 - Census tract is used as the HL7 identifier for the user-defined table of values for this component. Allowable Values: codes defined by government. Different <name/address types> and representations of the same name/address should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: Also note that this new component remains in "alphabetic" representation with each repetition of the fields using these data types. I.e. even though the address may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component cannot be fully expressed. Identified as v 2.4 erratum. Retained for backward compatibility only as of v 2.5. Refer to Effective Date and Expiration Date components. This component contains the start and end date/times, which define the period in which this address was valid. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Phone Number Specifies the telephone number in a predetermined format that includes an optional extension, beeper number and comment. This component has been retained for backward compatibility only as of version 2.3. Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C any text] Note: Because this component has been deprecated a new data type has not been defined to replace the formatted ST. A code that represents a specific use of a telecommunication number. Refer to HL7 Table 0201 - Telecommunication use code for valid values. A code that represents the type of telecommunication equipment. Refer to HL7 Table 0202 - Telecommunication equipment type for valid values. Internationalization note: To make this data type interoperate with CEN’s Telecommunication data attribute group, we allow use of the second component for email addresses. The presence of an email address is specified by the addition of the value NET to the Phone Use Code table, and the type of Internet address is specified with the values Internet and X.400 to the Phone Equipment Type table. When used for an Internet address, the first component of the XTN data type will be null. If the @-sign is being used as a subcomponent delimiter, the HL7 subcomponent escape sequence may be used when encoding an Internet address (see Section Country Code (NM). Country Code Area/City Code Local Number Extension Contains comments with respect to the telephone number. The characters established within a company’s internal telephone system network used as a prefix to the Extension component for internal dialing. Note that the use of Extension Prefix requires that the Extension component be valued and that digits, as well as special characters (e.g., *, #) may be used. The characters established within a company’s internal telephone system used in place of the (external) telephone number to facilitate calling because its length is shorter than that of the telephone number. Note that digits, as well as special characters (e.g., *, #) may be used. An expression of the telephone number as an unparsible string. The phone number was entered as free text and sending system does not know how to parse it. Business Phone Number Specifies the telephone number in a predetermined format that includes an optional extension, beeper number and comment. This component has been retained for backward compatibility only as of version 2.3. Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C any text] Note: Because this component has been deprecated a new data type has not been defined to replace the formatted ST. A code that represents a specific use of a telecommunication number. Refer to HL7 Table 0201 - Telecommunication use code for valid values. A code that represents the type of telecommunication equipment. Refer to HL7 Table 0202 - Telecommunication equipment type for valid values. Internationalization note: To make this data type interoperate with CEN’s Telecommunication data attribute group, we allow use of the second component for email addresses. The presence of an email address is specified by the addition of the value NET to the Phone Use Code table, and the type of Internet address is specified with the values Internet and X.400 to the Phone Equipment Type table. When used for an Internet address, the first component of the XTN data type will be null. If the @-sign is being used as a subcomponent delimiter, the HL7 subcomponent escape sequence may be used when encoding an Internet address (see Section Country Code (NM). Country Code Area/City Code Local Number Extension Contains comments with respect to the telephone number. The characters established within a company’s internal telephone system network used as a prefix to the Extension component for internal dialing. Note that the use of Extension Prefix requires that the Extension component be valued and that digits, as well as special characters (e.g., *, #) may be used. The characters established within a company’s internal telephone system used in place of the (external) telephone number to facilitate calling because its length is shorter than that of the telephone number. Note that digits, as well as special characters (e.g., *, #) may be used. An expression of the telephone number as an unparsible string. The phone number was entered as free text and sending system does not know how to parse it. Contact Role Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Start Date End Date Next of Kin / Associated Parties Job Title Next of Kin / Associated Parties Job Code/Class This component contains the person’s job code. User-defined Table 0327 - Job code is used as the HL7 identifier for the user-defined table of values for this component. This component contains the person’s employee classification. Refer to User-defined Table 0328 - Employee classification for suggested values. This component contains the text of the job description. This will accommodate systems where job descriptions are not codified. Next of Kin / Associated Parties Employee Number The value of the identifier itself. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. The algorithm for calculating a Mod10 check digit is as follows: Assume you have an identifier - 12345. Take the odd digit positions, counting from the right, i.e., 531, multiply this number by 2 to get 1062. Take the even digit positions, starting from the right (i.e., 42), prepend these to the 1062 to get 421062. Add all of these six digits together to get 15. Subtract this number from the next highest multiple of 10, i.e., 20 - 15 to get 5. The Mod10 check digit is 5. The Mod10 check digit for 401 is 0; for 9999, it’s 4; for 99999999, it’s 8. The algorithm for calculating a Mod11 check digit is as follows: Terms d = digit of number starting from units digit, followed by 10’s position, followed by 100’s position, etc. w = weight of digit position starting with the units position, followed by 10’s position, followed by 100’s position etc. Values for w = 2, 3, 4, 5, 6, 7, 2, 3, 4, 5, 6, 7, etc. (repeats for each group of 6 digits) c = check digit Calculation (Step 1) m = sum of (d * w) for positions 1, 2, etc. starting with units digit for d = digit value starting with units position to highest order for w = weight value from 2 to 7 for every six positions starting with units digit (Step 2) c1 = m mod 11 (Step 3) if c1 = 0 then reset c1 = 1 (Step 4) = (11 - c1) mod 10 Example: If the number is 1234567, then the mod 11 check digit = 4 The calculations are: M = (7*2)+(6*3)+(5*4)+(4*5)+(3*6)+(2*7)+(1*2) = 14 + 18 + 20 + 20 + 18 + 14 + 2 = 106 c1 = 106 mod 11 = 7 c = (11-c1) mod 10 = 4 mod 10 = 4 Other variants of these check digit algorithms exist and may be used by local bilateral site agreement. Note: The check digit and code identifying check digit scheme are null if ID is alphanumeric. The assigning authority is a unique name of the system (or organization or agency or department) that creates the data. . Refer to User-defined Table 0363 – Assigning authority for suggested values. The reader is referred to the CX.9 and the CX.10 if there is a need to transmit values with semantic meaning for an assigning jurisdiction or assigning department or agency in addition to, or instead of, an assigning authority. However, all 3 components may be valued. If, in so doing, it is discovered that the values in CX.9 and/or CX.10 conflict with CX.4, the user would look to the Message Profile or other implementation agreement for a statement as to which takes precedence. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the patient. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component), may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The first date, if known, on which the identifier is valid and active. The last date, if known, on which the identifier is valid and active. The geo-political body that assigned the identifier in component 1. Refer to HL7 Table 0399 Country Code in section 2.15.9.17 for valid values if the administrative unit under whose jurisdiction the identifier was issued is a country. Refer to User-Defined Table 0347 State/Province for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a state or province. This table is country specific. In the US postal codes may be used. Refer to User-defined Table –0289 County/Parish for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a county or parish. The reader is referred to the CX.4, if there is a need to transmit this information as an OID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. Refer to User-defined Table –0530 Organizations, Agency, Department for suggested values if the administrative unit under whose jurisdiction the identifier was issued is an organization, agency or department. This is populated with site-specific assigning authorities. It also should contain national or international codes when CX-5 Identifier Type may be assigned by more than one authority within a governmental or organizational unit. For example, a federal government may have 2 departments that assign a military identifier, its Veterans Affairs department and its department of defense. It is not recommended to include values for entities such as Social Security Administration (SSA), Immigration and Naturalization Service (INS), Center for Medicare and Medicaid Services (CMS) because they are included in the identifier type table. In these cases the name of the country plus the identifier type yields the correct interpretation of the identifier in component one. Likewise, entries like department of motor vehicles (DMV) and licensing boards are not recommended for inclusion because the combination of state and identifier type yields the correct interpretation of the identifier in component one. This approach is not to be confused with the detailed information provided in the chapter 15 segments that have provision for specifying the precise granting body and issuing body information needed in personnel management messages. Example 1: <Identifier> plus <Visa> yields a unique identifier. Example 2: <Identifier> plus <state> plus <DLN> yields a unique driver’s license number. Example 3: <Identifier> plus <country> plus <INS> yields a unique immigration number. The reader is referred to the CX.4, if there is a need to transmit this information as an OID. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Organization Name - NK1 The name of the specified organization. A code that represents the type of name i.e., legal name, display name. Refer to User-defined Table 0204 - Organizational Name Type for suggested values. This component has been retained for backward compatibility only as of v 2.5. It is recommended to use component 10 Organization identifier that accommodates alphanumeric identifiers. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. The check digit scheme codes are defined in HL7 Table 0061 - Check digit scheme. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Assigning authorities are unique across a given HL7 implementation. Refer to User-defined Table 0363 - Assigning Authority for suggested values. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e. even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation code for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component contains the sequence of characters (the code) that uniquely identifies the item being referenced by XON.1 Organization Name. This component replaces XON.3 ID Number as of v 2.5. Note: The check digit and code identifying check digit scheme are null if Organization identifier is alphanumeric. Marital Status Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Administrative Sex Date/Time of Birth The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Living Dependency Ambulatory Status Citizenship Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Primary Language Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Living Arrangement Publicity Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Protection Indicator Student Indicator Religion Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Mother's Maiden Name This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, "FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. This component cannot be fully expressed. Identified as v 2.4 erratum. Retained for backward compatibility only as of v 2.5. Refer to Effective Date and Expiration Date components. This component contains the start and end date/times, which define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 0444 – Name assembly order for valid values. The first date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. Nationality Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Ethnic Group Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Contact Reason Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Contact Person's Name This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, "FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. This component cannot be fully expressed. Identified as v 2.4 erratum. Retained for backward compatibility only as of v 2.5. Refer to Effective Date and Expiration Date components. This component contains the start and end date/times, which define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 0444 – Name assembly order for valid values. The first date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. Contact Person's Telephone Number Specifies the telephone number in a predetermined format that includes an optional extension, beeper number and comment. This component has been retained for backward compatibility only as of version 2.3. Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C any text] Note: Because this component has been deprecated a new data type has not been defined to replace the formatted ST. A code that represents a specific use of a telecommunication number. Refer to HL7 Table 0201 - Telecommunication use code for valid values. A code that represents the type of telecommunication equipment. Refer to HL7 Table 0202 - Telecommunication equipment type for valid values. Internationalization note: To make this data type interoperate with CEN’s Telecommunication data attribute group, we allow use of the second component for email addresses. The presence of an email address is specified by the addition of the value NET to the Phone Use Code table, and the type of Internet address is specified with the values Internet and X.400 to the Phone Equipment Type table. When used for an Internet address, the first component of the XTN data type will be null. If the @-sign is being used as a subcomponent delimiter, the HL7 subcomponent escape sequence may be used when encoding an Internet address (see Section Country Code (NM). Country Code Area/City Code Local Number Extension Contains comments with respect to the telephone number. The characters established within a company’s internal telephone system network used as a prefix to the Extension component for internal dialing. Note that the use of Extension Prefix requires that the Extension component be valued and that digits, as well as special characters (e.g., *, #) may be used. The characters established within a company’s internal telephone system used in place of the (external) telephone number to facilitate calling because its length is shorter than that of the telephone number. Note that digits, as well as special characters (e.g., *, #) may be used. An expression of the telephone number as an unparsible string. The phone number was entered as free text and sending system does not know how to parse it. Contact Person's Address See section 2.A.67, "SAD – street address" for description of components. This component specifies the street or mailing address of a person or institution. When referencing an institution, this first component is used to specify the institution name. When used in connection with a person, this component specifies the first line of the address. Street Name Dwelling Number Second line of address. In US usage, it qualifies address. Examples: Suite 555 or Fourth Floor. When referencing an institution, this component specifies the street address. This component specifies the city, or district or place where the addressee is located depending upon the national convention for formatting addresses for postal usage. This component specifies the state or province where the addressee is located. State or province should be represented by the official postal service codes for that country. This component specifies the zip or postal code where the addressee is located. Zip or postal codes should be represented by the official codes for that country. In the US, the zip code takes the form 99999[-9999], while the Canadian postal code takes the form A9A9A9, and the Australian Postcode takes the form 9999. This component specifies the country where the addressee is locatedHL7 specifies that the 3-character (alphabetic) form of ISO 3166 be used for the country code. Refer to HL7 Table 0399 – Country code in section 2.15.9.17 for valid values. This component specifies the kind or type of address. Refer to HL7 Table 0190 - Address type for valid values. This component specifies any other geographic designation. It includes county, bioregion, SMSA, etc. A code that represents the county in which the specified address resides. User-defined Table 0289 - County/parish is used as the HL7 identifier for the user-defined table of values for this component. When this component is used to represent the county (or parish), component 8 <other geographic designation> should not duplicate it (i.e., the use of <other geographic designation> to represent the county is allowed only for the purpose of backward compatibility, and should be discouraged in this and future versions of HL7). Allowable values: codes defined by government. A code that represents the census tract in which the specified address resides. User-defined Table 0288 - Census tract is used as the HL7 identifier for the user-defined table of values for this component. Allowable Values: codes defined by government. Different <name/address types> and representations of the same name/address should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: Also note that this new component remains in "alphabetic" representation with each repetition of the fields using these data types. I.e. even though the address may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component cannot be fully expressed. Identified as v 2.4 erratum. Retained for backward compatibility only as of v 2.5. Refer to Effective Date and Expiration Date components. This component contains the start and end date/times, which define the period in which this address was valid. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Next of Kin/Associated Party's Identifiers The value of the identifier itself. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. The algorithm for calculating a Mod10 check digit is as follows: Assume you have an identifier - 12345. Take the odd digit positions, counting from the right, i.e., 531, multiply this number by 2 to get 1062. Take the even digit positions, starting from the right (i.e., 42), prepend these to the 1062 to get 421062. Add all of these six digits together to get 15. Subtract this number from the next highest multiple of 10, i.e., 20 - 15 to get 5. The Mod10 check digit is 5. The Mod10 check digit for 401 is 0; for 9999, it’s 4; for 99999999, it’s 8. The algorithm for calculating a Mod11 check digit is as follows: Terms d = digit of number starting from units digit, followed by 10’s position, followed by 100’s position, etc. w = weight of digit position starting with the units position, followed by 10’s position, followed by 100’s position etc. Values for w = 2, 3, 4, 5, 6, 7, 2, 3, 4, 5, 6, 7, etc. (repeats for each group of 6 digits) c = check digit Calculation (Step 1) m = sum of (d * w) for positions 1, 2, etc. starting with units digit for d = digit value starting with units position to highest order for w = weight value from 2 to 7 for every six positions starting with units digit (Step 2) c1 = m mod 11 (Step 3) if c1 = 0 then reset c1 = 1 (Step 4) = (11 - c1) mod 10 Example: If the number is 1234567, then the mod 11 check digit = 4 The calculations are: M = (7*2)+(6*3)+(5*4)+(4*5)+(3*6)+(2*7)+(1*2) = 14 + 18 + 20 + 20 + 18 + 14 + 2 = 106 c1 = 106 mod 11 = 7 c = (11-c1) mod 10 = 4 mod 10 = 4 Other variants of these check digit algorithms exist and may be used by local bilateral site agreement. Note: The check digit and code identifying check digit scheme are null if ID is alphanumeric. The assigning authority is a unique name of the system (or organization or agency or department) that creates the data. . Refer to User-defined Table 0363 – Assigning authority for suggested values. The reader is referred to the CX.9 and the CX.10 if there is a need to transmit values with semantic meaning for an assigning jurisdiction or assigning department or agency in addition to, or instead of, an assigning authority. However, all 3 components may be valued. If, in so doing, it is discovered that the values in CX.9 and/or CX.10 conflict with CX.4, the user would look to the Message Profile or other implementation agreement for a statement as to which takes precedence. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the patient. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component), may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The first date, if known, on which the identifier is valid and active. The last date, if known, on which the identifier is valid and active. The geo-political body that assigned the identifier in component 1. Refer to HL7 Table 0399 Country Code in section 2.15.9.17 for valid values if the administrative unit under whose jurisdiction the identifier was issued is a country. Refer to User-Defined Table 0347 State/Province for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a state or province. This table is country specific. In the US postal codes may be used. Refer to User-defined Table –0289 County/Parish for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a county or parish. The reader is referred to the CX.4, if there is a need to transmit this information as an OID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. Refer to User-defined Table –0530 Organizations, Agency, Department for suggested values if the administrative unit under whose jurisdiction the identifier was issued is an organization, agency or department. This is populated with site-specific assigning authorities. It also should contain national or international codes when CX-5 Identifier Type may be assigned by more than one authority within a governmental or organizational unit. For example, a federal government may have 2 departments that assign a military identifier, its Veterans Affairs department and its department of defense. It is not recommended to include values for entities such as Social Security Administration (SSA), Immigration and Naturalization Service (INS), Center for Medicare and Medicaid Services (CMS) because they are included in the identifier type table. In these cases the name of the country plus the identifier type yields the correct interpretation of the identifier in component one. Likewise, entries like department of motor vehicles (DMV) and licensing boards are not recommended for inclusion because the combination of state and identifier type yields the correct interpretation of the identifier in component one. This approach is not to be confused with the detailed information provided in the chapter 15 segments that have provision for specifying the precise granting body and issuing body information needed in personnel management messages. Example 1: <Identifier> plus <Visa> yields a unique identifier. Example 2: <Identifier> plus <state> plus <DLN> yields a unique driver’s license number. Example 3: <Identifier> plus <country> plus <INS> yields a unique immigration number. The reader is referred to the CX.4, if there is a need to transmit this information as an OID. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Job Status Race Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Handicap Contact Person Social Security Number Next of Kin Birth Place VIP Indicator - Set ID. Dit veld bevat het nummer dat dit segment identificeert binnen het bericht. Bij de eerste keer dat het segment voorkomt, moet het volgnummer 1 zijn, bij de tweede keer is het 2, enzovoorts. Patient Class. Verplicht veld in HL7. Opmerking: wordt door RIVM Type-Ned en ISIS-AR niet gebruikt. Hier de bij de zender bekende waarde plaatsen, of anders de waarde N (Not Applicable). Assigned Patient Location. PV1-3-4: Facility (HD)Bevat de code van de (fysieke locatie van de) zorginstelling. Voor RIVM Type-Ned en RIVM ISIS-AR verplicht indien dit een ziekenhuis of een verpleeghuis betreft (dus voorlopig niet voor huisartsen of andere zorginstellingen). Echter: bij gebrek aan een voldoende complete landelijke lijst voor dit doel is dit veld voor deze systemen vooralsnog niet verplicht te stellen.PV1-3-6: Person Location TypeType afdeling binnen het ziekenhuis waar de patient verbleef ten tijde van de afname van het materiaal. Zie RIVM Type-Ned en ISIS-AR Type Afdeling voor geldige waarden. - - - Bevat de code van de (fysieke locatie van de) zorginstelling. Voor ISIS-AR verplicht indien dit een ziekenhuis of een verpleeghuis betreft (dus voorlopig niet voor huisartsen of andere zorginstellingen). Echter: bij gebrek aan een voldoende complete landelijke lijst voor dit doel is dit veld voor deze systemen vooralsnog niet verplicht te stellen. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. - Type afdeling binnen het ziekenhuis waar de patiënt verbleef ten tijde van de afname van het materiaal. Voor communicatie met het RIVM, geldt een specifieke lijst van afdelingscodes. De op moment van specificeren geldende lijst is gekoppeld. - - - - The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. - User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Admission Type Preadmit Number The value of the identifier itself. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. The algorithm for calculating a Mod10 check digit is as follows: Assume you have an identifier - 12345. Take the odd digit positions, counting from the right, i.e., 531, multiply this number by 2 to get 1062. Take the even digit positions, starting from the right (i.e., 42), prepend these to the 1062 to get 421062. Add all of these six digits together to get 15. Subtract this number from the next highest multiple of 10, i.e., 20 - 15 to get 5. The Mod10 check digit is 5. The Mod10 check digit for 401 is 0; for 9999, it’s 4; for 99999999, it’s 8. The algorithm for calculating a Mod11 check digit is as follows: Terms d = digit of number starting from units digit, followed by 10’s position, followed by 100’s position, etc. w = weight of digit position starting with the units position, followed by 10’s position, followed by 100’s position etc. Values for w = 2, 3, 4, 5, 6, 7, 2, 3, 4, 5, 6, 7, etc. (repeats for each group of 6 digits) c = check digit Calculation (Step 1) m = sum of (d * w) for positions 1, 2, etc. starting with units digit for d = digit value starting with units position to highest order for w = weight value from 2 to 7 for every six positions starting with units digit (Step 2) c1 = m mod 11 (Step 3) if c1 = 0 then reset c1 = 1 (Step 4) = (11 - c1) mod 10 Example: If the number is 1234567, then the mod 11 check digit = 4 The calculations are: M = (7*2)+(6*3)+(5*4)+(4*5)+(3*6)+(2*7)+(1*2) = 14 + 18 + 20 + 20 + 18 + 14 + 2 = 106 c1 = 106 mod 11 = 7 c = (11-c1) mod 10 = 4 mod 10 = 4 Other variants of these check digit algorithms exist and may be used by local bilateral site agreement. Note: The check digit and code identifying check digit scheme are null if ID is alphanumeric. The assigning authority is a unique name of the system (or organization or agency or department) that creates the data. . Refer to User-defined Table 0363 – Assigning authority for suggested values. The reader is referred to the CX.9 and the CX.10 if there is a need to transmit values with semantic meaning for an assigning jurisdiction or assigning department or agency in addition to, or instead of, an assigning authority. However, all 3 components may be valued. If, in so doing, it is discovered that the values in CX.9 and/or CX.10 conflict with CX.4, the user would look to the Message Profile or other implementation agreement for a statement as to which takes precedence. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the patient. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component), may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The first date, if known, on which the identifier is valid and active. The last date, if known, on which the identifier is valid and active. The geo-political body that assigned the identifier in component 1. Refer to HL7 Table 0399 Country Code in section 2.15.9.17 for valid values if the administrative unit under whose jurisdiction the identifier was issued is a country. Refer to User-Defined Table 0347 State/Province for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a state or province. This table is country specific. In the US postal codes may be used. Refer to User-defined Table –0289 County/Parish for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a county or parish. The reader is referred to the CX.4, if there is a need to transmit this information as an OID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. Refer to User-defined Table –0530 Organizations, Agency, Department for suggested values if the administrative unit under whose jurisdiction the identifier was issued is an organization, agency or department. This is populated with site-specific assigning authorities. It also should contain national or international codes when CX-5 Identifier Type may be assigned by more than one authority within a governmental or organizational unit. For example, a federal government may have 2 departments that assign a military identifier, its Veterans Affairs department and its department of defense. It is not recommended to include values for entities such as Social Security Administration (SSA), Immigration and Naturalization Service (INS), Center for Medicare and Medicaid Services (CMS) because they are included in the identifier type table. In these cases the name of the country plus the identifier type yields the correct interpretation of the identifier in component one. Likewise, entries like department of motor vehicles (DMV) and licensing boards are not recommended for inclusion because the combination of state and identifier type yields the correct interpretation of the identifier in component one. This approach is not to be confused with the detailed information provided in the chapter 15 segments that have provision for specifying the precise granting body and issuing body information needed in personnel management messages. Example 1: <Identifier> plus <Visa> yields a unique identifier. Example 2: <Identifier> plus <state> plus <DLN> yields a unique driver’s license number. Example 3: <Identifier> plus <country> plus <INS> yields a unique immigration number. The reader is referred to the CX.4, if there is a need to transmit this information as an OID. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Prior Patient Location This component specifies the code for the point where patient care is administered. It is conditional on PL.6 Person Location Type (e.g., nursing unit or department or clinic). After floor, it is the most general patient location designation. Refer to User-defined Table 0302 - Point of care for suggested values. This component specifies the code for the patient's room. After point of care, it is the most general person location designation. Refer to User-defined Table 0303 - Room for suggested values. This component specifies the code for the patient's bed. After room, it is the most general person location designation. Refer to User-defined Table 0304 - Bed for suggested values. This component is subject to site interpretation but generally describes the highest level physical designation of an institution, medical center or enterprise. It is the most general person location designation. (See Section 2.A.33, "HD - hierarchic designator") for discussion of data type. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be redefined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. This component specifies the code for the status or availability of the location. For example, it may convey bed status. Refer to User-defined Table 0306 - Location status for suggested values. Person location type is the categorization of the person’s location defined by facility, building, floor, point of care, room or bed. Although not a required field, when used, it may be the only populated field. It usually includes values such as nursing unit, department, clinic, SNF, physician’s office. Refer to User-defined Table 0305 - Person location type for suggested values. Required if known This component specifies the code for the building where the person is located. After facility, it is the most general person location designation. Refer to User-defined Table 0307 - Building for suggested values. This component specifies the code for the floor where the person is located. After building, it is the most general person location designation. Refer to User-defined Table 0308 - Floor for suggested values. This component describes the location in free text. The unique identifier that represents the physical location as a whole without regard for the individual components. This accommodates sites that may have a different method of defining physical units or who may code at a less granular level. For example, point of care, room, and bed may be 1 indivisible code. The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The entity that creates the data for the individual physical location components. If populated, it should be the authority for all components populated. Refer to User-defined Table 0363 – Assigning authority for suggested values for the first sub-component of the HD component, <namespace ID>. This component makes it possible for codes to be differentiated when the field in which this data type is used repeats. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementors may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Attending Doctor This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Referring Doctor This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Consulting Doctor This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Specialisme van de hoofdbehandelaar van de patiënt volgens UZI-rolcode. Temporary Location This component specifies the code for the point where patient care is administered. It is conditional on PL.6 Person Location Type (e.g., nursing unit or department or clinic). After floor, it is the most general patient location designation. Refer to User-defined Table 0302 - Point of care for suggested values. This component specifies the code for the patient's room. After point of care, it is the most general person location designation. Refer to User-defined Table 0303 - Room for suggested values. This component specifies the code for the patient's bed. After room, it is the most general person location designation. Refer to User-defined Table 0304 - Bed for suggested values. This component is subject to site interpretation but generally describes the highest level physical designation of an institution, medical center or enterprise. It is the most general person location designation. (See Section 2.A.33, "HD - hierarchic designator") for discussion of data type. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be redefined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. This component specifies the code for the status or availability of the location. For example, it may convey bed status. Refer to User-defined Table 0306 - Location status for suggested values. Person location type is the categorization of the person’s location defined by facility, building, floor, point of care, room or bed. Although not a required field, when used, it may be the only populated field. It usually includes values such as nursing unit, department, clinic, SNF, physician’s office. Refer to User-defined Table 0305 - Person location type for suggested values. Required if known This component specifies the code for the building where the person is located. After facility, it is the most general person location designation. Refer to User-defined Table 0307 - Building for suggested values. This component specifies the code for the floor where the person is located. After building, it is the most general person location designation. Refer to User-defined Table 0308 - Floor for suggested values. This component describes the location in free text. The unique identifier that represents the physical location as a whole without regard for the individual components. This accommodates sites that may have a different method of defining physical units or who may code at a less granular level. For example, point of care, room, and bed may be 1 indivisible code. The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The entity that creates the data for the individual physical location components. If populated, it should be the authority for all components populated. Refer to User-defined Table 0363 – Assigning authority for suggested values for the first sub-component of the HD component, <namespace ID>. This component makes it possible for codes to be differentiated when the field in which this data type is used repeats. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementors may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Preadmit Test Indicator Re-admission Indicator Admit Source Ambulatory Status VIP Indicator Admitting Doctor This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Patient Type Visit Number The value of the identifier itself. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. The algorithm for calculating a Mod10 check digit is as follows: Assume you have an identifier - 12345. Take the odd digit positions, counting from the right, i.e., 531, multiply this number by 2 to get 1062. Take the even digit positions, starting from the right (i.e., 42), prepend these to the 1062 to get 421062. Add all of these six digits together to get 15. Subtract this number from the next highest multiple of 10, i.e., 20 - 15 to get 5. The Mod10 check digit is 5. The Mod10 check digit for 401 is 0; for 9999, it’s 4; for 99999999, it’s 8. The algorithm for calculating a Mod11 check digit is as follows: Terms d = digit of number starting from units digit, followed by 10’s position, followed by 100’s position, etc. w = weight of digit position starting with the units position, followed by 10’s position, followed by 100’s position etc. Values for w = 2, 3, 4, 5, 6, 7, 2, 3, 4, 5, 6, 7, etc. (repeats for each group of 6 digits) c = check digit Calculation (Step 1) m = sum of (d * w) for positions 1, 2, etc. starting with units digit for d = digit value starting with units position to highest order for w = weight value from 2 to 7 for every six positions starting with units digit (Step 2) c1 = m mod 11 (Step 3) if c1 = 0 then reset c1 = 1 (Step 4) = (11 - c1) mod 10 Example: If the number is 1234567, then the mod 11 check digit = 4 The calculations are: M = (7*2)+(6*3)+(5*4)+(4*5)+(3*6)+(2*7)+(1*2) = 14 + 18 + 20 + 20 + 18 + 14 + 2 = 106 c1 = 106 mod 11 = 7 c = (11-c1) mod 10 = 4 mod 10 = 4 Other variants of these check digit algorithms exist and may be used by local bilateral site agreement. Note: The check digit and code identifying check digit scheme are null if ID is alphanumeric. The assigning authority is a unique name of the system (or organization or agency or department) that creates the data. . Refer to User-defined Table 0363 – Assigning authority for suggested values. The reader is referred to the CX.9 and the CX.10 if there is a need to transmit values with semantic meaning for an assigning jurisdiction or assigning department or agency in addition to, or instead of, an assigning authority. However, all 3 components may be valued. If, in so doing, it is discovered that the values in CX.9 and/or CX.10 conflict with CX.4, the user would look to the Message Profile or other implementation agreement for a statement as to which takes precedence. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the patient. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component), may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The first date, if known, on which the identifier is valid and active. The last date, if known, on which the identifier is valid and active. The geo-political body that assigned the identifier in component 1. Refer to HL7 Table 0399 Country Code in section 2.15.9.17 for valid values if the administrative unit under whose jurisdiction the identifier was issued is a country. Refer to User-Defined Table 0347 State/Province for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a state or province. This table is country specific. In the US postal codes may be used. Refer to User-defined Table –0289 County/Parish for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a county or parish. The reader is referred to the CX.4, if there is a need to transmit this information as an OID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. Refer to User-defined Table –0530 Organizations, Agency, Department for suggested values if the administrative unit under whose jurisdiction the identifier was issued is an organization, agency or department. This is populated with site-specific assigning authorities. It also should contain national or international codes when CX-5 Identifier Type may be assigned by more than one authority within a governmental or organizational unit. For example, a federal government may have 2 departments that assign a military identifier, its Veterans Affairs department and its department of defense. It is not recommended to include values for entities such as Social Security Administration (SSA), Immigration and Naturalization Service (INS), Center for Medicare and Medicaid Services (CMS) because they are included in the identifier type table. In these cases the name of the country plus the identifier type yields the correct interpretation of the identifier in component one. Likewise, entries like department of motor vehicles (DMV) and licensing boards are not recommended for inclusion because the combination of state and identifier type yields the correct interpretation of the identifier in component one. This approach is not to be confused with the detailed information provided in the chapter 15 segments that have provision for specifying the precise granting body and issuing body information needed in personnel management messages. Example 1: <Identifier> plus <Visa> yields a unique identifier. Example 2: <Identifier> plus <state> plus <DLN> yields a unique driver’s license number. Example 3: <Identifier> plus <country> plus <INS> yields a unique immigration number. The reader is referred to the CX.4, if there is a need to transmit this information as an OID. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Financial Class This component contains the financial class assigned to a person. User-defined Table 0064 - Financial class is used as the HL7 identifier for the user-defined table of values for this component. This component contains the effective date/time of the person’s assignment to the financial class specified in the first component. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Charge Price Indicator Courtesy Code Credit Rating Contract Code Contract Effective Date Contract Amount Contract Period Interest Code Transfer to Bad Debt Code Transfer to Bad Debt Date Bad Debt Agency Code Bad Debt Transfer Amount Bad Debt Recovery Amount Delete Account Indicator Delete Account Date Discharge Disposition Discharged to Location Specifies the healthcare facility to which the patient was discharged. Refer to User-defined Table 0113 - Discharged to location for suggested values. Specifies the date on which the patient was discharged to a healthcare facility. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Diet Type Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Verplicht voor ISIS-AR. Bevat het instellingstype van de zorglocatie volgens ISIS-AR codering. Bed Status Account Status Pending Location This component specifies the code for the point where patient care is administered. It is conditional on PL.6 Person Location Type (e.g., nursing unit or department or clinic). After floor, it is the most general patient location designation. Refer to User-defined Table 0302 - Point of care for suggested values. This component specifies the code for the patient's room. After point of care, it is the most general person location designation. Refer to User-defined Table 0303 - Room for suggested values. This component specifies the code for the patient's bed. After room, it is the most general person location designation. Refer to User-defined Table 0304 - Bed for suggested values. This component is subject to site interpretation but generally describes the highest level physical designation of an institution, medical center or enterprise. It is the most general person location designation. (See Section 2.A.33, "HD - hierarchic designator") for discussion of data type. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be redefined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. This component specifies the code for the status or availability of the location. For example, it may convey bed status. Refer to User-defined Table 0306 - Location status for suggested values. Person location type is the categorization of the person’s location defined by facility, building, floor, point of care, room or bed. Although not a required field, when used, it may be the only populated field. It usually includes values such as nursing unit, department, clinic, SNF, physician’s office. Refer to User-defined Table 0305 - Person location type for suggested values. Required if known This component specifies the code for the building where the person is located. After facility, it is the most general person location designation. Refer to User-defined Table 0307 - Building for suggested values. This component specifies the code for the floor where the person is located. After building, it is the most general person location designation. Refer to User-defined Table 0308 - Floor for suggested values. This component describes the location in free text. The unique identifier that represents the physical location as a whole without regard for the individual components. This accommodates sites that may have a different method of defining physical units or who may code at a less granular level. For example, point of care, room, and bed may be 1 indivisible code. The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The entity that creates the data for the individual physical location components. If populated, it should be the authority for all components populated. Refer to User-defined Table 0363 – Assigning authority for suggested values for the first sub-component of the HD component, <namespace ID>. This component makes it possible for codes to be differentiated when the field in which this data type is used repeats. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementors may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Prior Temporary Location This component specifies the code for the point where patient care is administered. It is conditional on PL.6 Person Location Type (e.g., nursing unit or department or clinic). After floor, it is the most general patient location designation. Refer to User-defined Table 0302 - Point of care for suggested values. This component specifies the code for the patient's room. After point of care, it is the most general person location designation. Refer to User-defined Table 0303 - Room for suggested values. This component specifies the code for the patient's bed. After room, it is the most general person location designation. Refer to User-defined Table 0304 - Bed for suggested values. This component is subject to site interpretation but generally describes the highest level physical designation of an institution, medical center or enterprise. It is the most general person location designation. (See Section 2.A.33, "HD - hierarchic designator") for discussion of data type. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be redefined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. This component specifies the code for the status or availability of the location. For example, it may convey bed status. Refer to User-defined Table 0306 - Location status for suggested values. Person location type is the categorization of the person’s location defined by facility, building, floor, point of care, room or bed. Although not a required field, when used, it may be the only populated field. It usually includes values such as nursing unit, department, clinic, SNF, physician’s office. Refer to User-defined Table 0305 - Person location type for suggested values. Required if known This component specifies the code for the building where the person is located. After facility, it is the most general person location designation. Refer to User-defined Table 0307 - Building for suggested values. This component specifies the code for the floor where the person is located. After building, it is the most general person location designation. Refer to User-defined Table 0308 - Floor for suggested values. This component describes the location in free text. The unique identifier that represents the physical location as a whole without regard for the individual components. This accommodates sites that may have a different method of defining physical units or who may code at a less granular level. For example, point of care, room, and bed may be 1 indivisible code. The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The entity that creates the data for the individual physical location components. If populated, it should be the authority for all components populated. Refer to User-defined Table 0363 – Assigning authority for suggested values for the first sub-component of the HD component, <namespace ID>. This component makes it possible for codes to be differentiated when the field in which this data type is used repeats. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementors may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Opnamedatum. Verplicht voor ISIS-AR indien van toepassing. Vullen indien bekend The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Discharge Date/Time The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Current Patient Balance Total Charges Total Adjustments Total Payments Alternate Visit ID The value of the identifier itself. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. The algorithm for calculating a Mod10 check digit is as follows: Assume you have an identifier - 12345. Take the odd digit positions, counting from the right, i.e., 531, multiply this number by 2 to get 1062. Take the even digit positions, starting from the right (i.e., 42), prepend these to the 1062 to get 421062. Add all of these six digits together to get 15. Subtract this number from the next highest multiple of 10, i.e., 20 - 15 to get 5. The Mod10 check digit is 5. The Mod10 check digit for 401 is 0; for 9999, it’s 4; for 99999999, it’s 8. The algorithm for calculating a Mod11 check digit is as follows: Terms d = digit of number starting from units digit, followed by 10’s position, followed by 100’s position, etc. w = weight of digit position starting with the units position, followed by 10’s position, followed by 100’s position etc. Values for w = 2, 3, 4, 5, 6, 7, 2, 3, 4, 5, 6, 7, etc. (repeats for each group of 6 digits) c = check digit Calculation (Step 1) m = sum of (d * w) for positions 1, 2, etc. starting with units digit for d = digit value starting with units position to highest order for w = weight value from 2 to 7 for every six positions starting with units digit (Step 2) c1 = m mod 11 (Step 3) if c1 = 0 then reset c1 = 1 (Step 4) = (11 - c1) mod 10 Example: If the number is 1234567, then the mod 11 check digit = 4 The calculations are: M = (7*2)+(6*3)+(5*4)+(4*5)+(3*6)+(2*7)+(1*2) = 14 + 18 + 20 + 20 + 18 + 14 + 2 = 106 c1 = 106 mod 11 = 7 c = (11-c1) mod 10 = 4 mod 10 = 4 Other variants of these check digit algorithms exist and may be used by local bilateral site agreement. Note: The check digit and code identifying check digit scheme are null if ID is alphanumeric. The assigning authority is a unique name of the system (or organization or agency or department) that creates the data. . Refer to User-defined Table 0363 – Assigning authority for suggested values. The reader is referred to the CX.9 and the CX.10 if there is a need to transmit values with semantic meaning for an assigning jurisdiction or assigning department or agency in addition to, or instead of, an assigning authority. However, all 3 components may be valued. If, in so doing, it is discovered that the values in CX.9 and/or CX.10 conflict with CX.4, the user would look to the Message Profile or other implementation agreement for a statement as to which takes precedence. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the patient. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component), may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The first date, if known, on which the identifier is valid and active. The last date, if known, on which the identifier is valid and active. The geo-political body that assigned the identifier in component 1. Refer to HL7 Table 0399 Country Code in section 2.15.9.17 for valid values if the administrative unit under whose jurisdiction the identifier was issued is a country. Refer to User-Defined Table 0347 State/Province for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a state or province. This table is country specific. In the US postal codes may be used. Refer to User-defined Table –0289 County/Parish for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a county or parish. The reader is referred to the CX.4, if there is a need to transmit this information as an OID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. Refer to User-defined Table –0530 Organizations, Agency, Department for suggested values if the administrative unit under whose jurisdiction the identifier was issued is an organization, agency or department. This is populated with site-specific assigning authorities. It also should contain national or international codes when CX-5 Identifier Type may be assigned by more than one authority within a governmental or organizational unit. For example, a federal government may have 2 departments that assign a military identifier, its Veterans Affairs department and its department of defense. It is not recommended to include values for entities such as Social Security Administration (SSA), Immigration and Naturalization Service (INS), Center for Medicare and Medicaid Services (CMS) because they are included in the identifier type table. In these cases the name of the country plus the identifier type yields the correct interpretation of the identifier in component one. Likewise, entries like department of motor vehicles (DMV) and licensing boards are not recommended for inclusion because the combination of state and identifier type yields the correct interpretation of the identifier in component one. This approach is not to be confused with the detailed information provided in the chapter 15 segments that have provision for specifying the precise granting body and issuing body information needed in personnel management messages. Example 1: <Identifier> plus <Visa> yields a unique identifier. Example 2: <Identifier> plus <state> plus <DLN> yields a unique driver’s license number. Example 3: <Identifier> plus <country> plus <INS> yields a unique immigration number. The reader is referred to the CX.4, if there is a need to transmit this information as an OID. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Visit Indicator Other Healthcare Provider This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Prior Pending Location This component specifies the code for the point where patient care is administered. It is conditional on PL.6 Person Location Type (e.g., nursing unit or department or clinic). After floor, it is the most general patient location designation. Refer to User-defined Table 0302 - Point of care for suggested values. This component specifies the code for the patient's room. After point of care, it is the most general person location designation. Refer to User-defined Table 0303 - Room for suggested values. This component specifies the code for the patient's bed. After room, it is the most general person location designation. Refer to User-defined Table 0304 - Bed for suggested values. This component is subject to site interpretation but generally describes the highest level physical designation of an institution, medical center or enterprise. It is the most general person location designation. (See Section 2.A.33, "HD - hierarchic designator") for discussion of data type. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be redefined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. This component specifies the code for the status or availability of the location. For example, it may convey bed status. Refer to User-defined Table 0306 - Location status for suggested values. Person location type is the categorization of the person’s location defined by facility, building, floor, point of care, room or bed. Although not a required field, when used, it may be the only populated field. It usually includes values such as nursing unit, department, clinic, SNF, physician’s office. Refer to User-defined Table 0305 - Person location type for suggested values. Required if known This component specifies the code for the building where the person is located. After facility, it is the most general person location designation. Refer to User-defined Table 0307 - Building for suggested values. This component specifies the code for the floor where the person is located. After building, it is the most general person location designation. Refer to User-defined Table 0308 - Floor for suggested values. This component describes the location in free text. The unique identifier that represents the physical location as a whole without regard for the individual components. This accommodates sites that may have a different method of defining physical units or who may code at a less granular level. For example, point of care, room, and bed may be 1 indivisible code. The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The entity that creates the data for the individual physical location components. If populated, it should be the authority for all components populated. Refer to User-defined Table 0363 – Assigning authority for suggested values for the first sub-component of the HD component, <namespace ID>. This component makes it possible for codes to be differentiated when the field in which this data type is used repeats. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementors may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Accommodation Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Admit Reason Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Transfer Reason Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Patient Valuables Patient Valuables Location Visit User Code Expected Admit Date/Time The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Expected Discharge Date/Time The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Estimated Length of Inpatient Stay Actual Length of Inpatient Stay Visit Description Referral Source Code This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Previous Service Date Employment Illness Related Indicator Purge Status Code Purge Status Date Special Program Code Retention Indicator Expected Number of Insurance Plans Visit Publicity Code Visit Protection Indicator Clinic Organization Name The name of the specified organization. A code that represents the type of name i.e., legal name, display name. Refer to User-defined Table 0204 - Organizational Name Type for suggested values. This component has been retained for backward compatibility only as of v 2.5. It is recommended to use component 10 Organization identifier that accommodates alphanumeric identifiers. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. The check digit scheme codes are defined in HL7 Table 0061 - Check digit scheme. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Assigning authorities are unique across a given HL7 implementation. Refer to User-defined Table 0363 - Assigning Authority for suggested values. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e. even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation code for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component contains the sequence of characters (the code) that uniquely identifies the item being referenced by XON.1 Organization Name. This component replaces XON.3 ID Number as of v 2.5. Note: The check digit and code identifying check digit scheme are null if Organization identifier is alphanumeric. Patient Status Code Visit Priority Code Previous Treatment Date Expected Discharge Disposition Signature on File Date First Similar Illness Date Patient Charge Adjustment Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Recurring Service Code Billing Media Code Expected Surgery Date and Time The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Military Partnership Code Military Non-Availability Code Newborn Baby Indicator Baby Detained Indicator Mode of Arrival Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Recreational Drug Use Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Admission Level of Care Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Precaution Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Patient Condition Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Living Will Code Organ Donor Code Advance Directive Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Patient Status Effective Date Expected LOA Return Date/Time The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Expected Pre-admission Testing Date/Time The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Notify Clergy Code - Set ID. Dit veld bevat het nummer dat dit segment identificeert binnen het bericht. Bij de eerste keer dat het segment voorkomt, moet het volgnummer 1 zijn, bij de tweede keer is het 2, enzovoorts. Insurance Plan ID. Veld werd voorheen niet gebruikt en zal vanaf 1-1-2006 de naam van de polis bij de verzekeraar gaan bevatten. De naam wordt in de 2e component van het CE datatype (Text) geplaatst. Als de naam van de polis niet bekend is, moet de waarde ‘null’ worden doorgegeven omdat het een verplicht veld is. Voorbeelden: Basispakket, Beter Af Plus Polis , Aanvullend Extra, Aanvullend ***, Regeling aanvullende vergoedingen. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Code van de verzekeringsmaatschappij, wordt een UZOVI code indien de code van Vektis gebruikt wordt. Indien gebruik gemaakt wordt van de Vektis tabel voor verzekeringsinstellingen, dan moet bij Assigning Authority ‘UZOVI’ worden vermeld. Anders moet hierin staan ‘LOCAL’. Het veld is herhalend, waardoor het mogelijk is om zowel de lokale code als de UZOVI-code te vermelden. The value of the identifier itself. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. The algorithm for calculating a Mod10 check digit is as follows: Assume you have an identifier - 12345. Take the odd digit positions, counting from the right, i.e., 531, multiply this number by 2 to get 1062. Take the even digit positions, starting from the right (i.e., 42), prepend these to the 1062 to get 421062. Add all of these six digits together to get 15. Subtract this number from the next highest multiple of 10, i.e., 20 - 15 to get 5. The Mod10 check digit is 5. The Mod10 check digit for 401 is 0; for 9999, it’s 4; for 99999999, it’s 8. The algorithm for calculating a Mod11 check digit is as follows: Terms d = digit of number starting from units digit, followed by 10’s position, followed by 100’s position, etc. w = weight of digit position starting with the units position, followed by 10’s position, followed by 100’s position etc. Values for w = 2, 3, 4, 5, 6, 7, 2, 3, 4, 5, 6, 7, etc. (repeats for each group of 6 digits) c = check digit Calculation (Step 1) m = sum of (d * w) for positions 1, 2, etc. starting with units digit for d = digit value starting with units position to highest order for w = weight value from 2 to 7 for every six positions starting with units digit (Step 2) c1 = m mod 11 (Step 3) if c1 = 0 then reset c1 = 1 (Step 4) = (11 - c1) mod 10 Example: If the number is 1234567, then the mod 11 check digit = 4 The calculations are: M = (7*2)+(6*3)+(5*4)+(4*5)+(3*6)+(2*7)+(1*2) = 14 + 18 + 20 + 20 + 18 + 14 + 2 = 106 c1 = 106 mod 11 = 7 c = (11-c1) mod 10 = 4 mod 10 = 4 Other variants of these check digit algorithms exist and may be used by local bilateral site agreement. Note: The check digit and code identifying check digit scheme are null if ID is alphanumeric. The assigning authority is a unique name of the system (or organization or agency or department) that creates the data. . Refer to User-defined Table 0363 – Assigning authority for suggested values. The reader is referred to the CX.9 and the CX.10 if there is a need to transmit values with semantic meaning for an assigning jurisdiction or assigning department or agency in addition to, or instead of, an assigning authority. However, all 3 components may be valued. If, in so doing, it is discovered that the values in CX.9 and/or CX.10 conflict with CX.4, the user would look to the Message Profile or other implementation agreement for a statement as to which takes precedence. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the patient. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component), may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The first date, if known, on which the identifier is valid and active. The last date, if known, on which the identifier is valid and active. The geo-political body that assigned the identifier in component 1. Refer to HL7 Table 0399 Country Code in section 2.15.9.17 for valid values if the administrative unit under whose jurisdiction the identifier was issued is a country. Refer to User-Defined Table 0347 State/Province for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a state or province. This table is country specific. In the US postal codes may be used. Refer to User-defined Table –0289 County/Parish for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a county or parish. The reader is referred to the CX.4, if there is a need to transmit this information as an OID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. Refer to User-defined Table –0530 Organizations, Agency, Department for suggested values if the administrative unit under whose jurisdiction the identifier was issued is an organization, agency or department. This is populated with site-specific assigning authorities. It also should contain national or international codes when CX-5 Identifier Type may be assigned by more than one authority within a governmental or organizational unit. For example, a federal government may have 2 departments that assign a military identifier, its Veterans Affairs department and its department of defense. It is not recommended to include values for entities such as Social Security Administration (SSA), Immigration and Naturalization Service (INS), Center for Medicare and Medicaid Services (CMS) because they are included in the identifier type table. In these cases the name of the country plus the identifier type yields the correct interpretation of the identifier in component one. Likewise, entries like department of motor vehicles (DMV) and licensing boards are not recommended for inclusion because the combination of state and identifier type yields the correct interpretation of the identifier in component one. This approach is not to be confused with the detailed information provided in the chapter 15 segments that have provision for specifying the precise granting body and issuing body information needed in personnel management messages. Example 1: <Identifier> plus <Visa> yields a unique identifier. Example 2: <Identifier> plus <state> plus <DLN> yields a unique driver’s license number. Example 3: <Identifier> plus <country> plus <INS> yields a unique immigration number. The reader is referred to the CX.4, if there is a need to transmit this information as an OID. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. De naam van de verzekeringsmaatschappij. In subveld 3 ID Number kan wederom de code van de verzeke-ringsmaatschappij worden opgenomen, maar deze mag niet in plaats van IN1-2 Insurance Plan ID worden gebruikt. Ook dit veld is herhalend waardoor zowel de Vektis-namen als de lokaal gebruikte namen kunnen worden vermeld. The name of the specified organization. A code that represents the type of name i.e., legal name, display name. Refer to User-defined Table 0204 - Organizational Name Type for suggested values. This component has been retained for backward compatibility only as of v 2.5. It is recommended to use component 10 Organization identifier that accommodates alphanumeric identifiers. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. The check digit scheme codes are defined in HL7 Table 0061 - Check digit scheme. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Assigning authorities are unique across a given HL7 implementation. Refer to User-defined Table 0363 - Assigning Authority for suggested values. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e. even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation code for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component contains the sequence of characters (the code) that uniquely identifies the item being referenced by XON.1 Organization Name. This component replaces XON.3 ID Number as of v 2.5. Note: The check digit and code identifying check digit scheme are null if Organization identifier is alphanumeric. Het adres van de verzekeringsmaatschappij. Adres straat - Vanaf versie 2.4 is ‘street address’ een samengesteld datatype, waar in de verschillende onderdelen van het adres in verschillende subcomponenten kunnen worden opgenomen This component specifies the street or mailing address of a person or institution. When referencing an institution, this first component is used to specify the institution name. When used in connection with a person, this component specifies the first line of the address. Street Name Dwelling Number Huisnummertoevoeging Woonplaats Staat of provincie. Meestal niet relevant, maar gebruiken bij plaatsnamen in meerdere provincies zoals Afferden (Gelderland en Limburg) en Bergen (Noord-Holland en Limburg) Postcode, indien een Nederlandse postcode dan zonder spaties dus bijv. 2316XA. Merk op dat de HL7v3 specificatie met een spatie voorschrijft. Er is hier bewust gekozen voor compatibiliteit met de officiële HL7v2.4 NL specificatie. Land Adrestype. Voor het eerste adres moet deze de waarde ‘M’ (mailing) hebben. Andere adressen kunnen ook worden doorgegeven, zoals bijv. huisadres (‘H’), of tijdelijk/verblijfsadres (‘C’). Andere geografische aanduiding. N.v.t. voor Nederlandse adressen County/graafschap code. N.v.t. voor Nederlandse adressen Census tract. N.v.t. voor Nederlandse adressen. Representatiecode adres. N.v.t. voor Nederlandse adressen Adres geldigheidsperiode. Hierin kunnen eventueel de begin- en einddatum worden doorgegeven waarbinnen een adres geldig is. Dit kan bijv. voor tijdelijke adressen relevant zijn. Het is echter gemarkeerd als obsoleet en behouden voor backward compatbility in versie 2.5. Zie in plaats daarvan XAD.13 en XAD.14. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. Geldigheidsdatum. De eerste datum, indien bekend, waarop het adres geldig is/was en actief. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Verloopdatum. De laatste datum, indien bekend, waarop het adres geldig is/was en actief. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Contactpersoon van de verzekerde bij de verzekeringsmaatschappij. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, "FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. This component cannot be fully expressed. Identified as v 2.4 erratum. Retained for backward compatibility only as of v 2.5. Refer to Effective Date and Expiration Date components. This component contains the start and end date/times, which define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 0444 – Name assembly order for valid values. The first date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. Telefoonummer van de verzekeringsmaatschappij. Specifies the telephone number in a predetermined format that includes an optional extension, beeper number and comment. This component has been retained for backward compatibility only as of version 2.3. Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C any text] Note: Because this component has been deprecated a new data type has not been defined to replace the formatted ST. A code that represents a specific use of a telecommunication number. Refer to HL7 Table 0201 - Telecommunication use code for valid values. A code that represents the type of telecommunication equipment. Refer to HL7 Table 0202 - Telecommunication equipment type for valid values. Internationalization note: To make this data type interoperate with CEN’s Telecommunication data attribute group, we allow use of the second component for email addresses. The presence of an email address is specified by the addition of the value NET to the Phone Use Code table, and the type of Internet address is specified with the values Internet and X.400 to the Phone Equipment Type table. When used for an Internet address, the first component of the XTN data type will be null. If the @-sign is being used as a subcomponent delimiter, the HL7 subcomponent escape sequence may be used when encoding an Internet address (see Section Country Code (NM). Country Code Area/City Code Local Number Extension Contains comments with respect to the telephone number. The characters established within a company’s internal telephone system network used as a prefix to the Extension component for internal dialing. Note that the use of Extension Prefix requires that the Extension component be valued and that digits, as well as special characters (e.g., *, #) may be used. The characters established within a company’s internal telephone system used in place of the (external) telephone number to facilitate calling because its length is shorter than that of the telephone number. Note that digits, as well as special characters (e.g., *, #) may be used. An expression of the telephone number as an unparsible string. The phone number was entered as free text and sending system does not know how to parse it. Het groepsnummer van de verzekering van de verzekerde. Kan bijvoorbeeld van toepassing zijn bij collectieve verzekeringen. De naam van de groep waarbinnen de verzekerde is verzekerd. The name of the specified organization. A code that represents the type of name i.e., legal name, display name. Refer to User-defined Table 0204 - Organizational Name Type for suggested values. This component has been retained for backward compatibility only as of v 2.5. It is recommended to use component 10 Organization identifier that accommodates alphanumeric identifiers. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. The check digit scheme codes are defined in HL7 Table 0061 - Check digit scheme. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Assigning authorities are unique across a given HL7 implementation. Refer to User-defined Table 0363 - Assigning Authority for suggested values. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e. even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation code for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component contains the sequence of characters (the code) that uniquely identifies the item being referenced by XON.1 Organization Name. This component replaces XON.3 ID Number as of v 2.5. Note: The check digit and code identifying check digit scheme are null if Organization identifier is alphanumeric. Insured's Group Emp ID The value of the identifier itself. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. The algorithm for calculating a Mod10 check digit is as follows: Assume you have an identifier - 12345. Take the odd digit positions, counting from the right, i.e., 531, multiply this number by 2 to get 1062. Take the even digit positions, starting from the right (i.e., 42), prepend these to the 1062 to get 421062. Add all of these six digits together to get 15. Subtract this number from the next highest multiple of 10, i.e., 20 - 15 to get 5. The Mod10 check digit is 5. The Mod10 check digit for 401 is 0; for 9999, it’s 4; for 99999999, it’s 8. The algorithm for calculating a Mod11 check digit is as follows: Terms d = digit of number starting from units digit, followed by 10’s position, followed by 100’s position, etc. w = weight of digit position starting with the units position, followed by 10’s position, followed by 100’s position etc. Values for w = 2, 3, 4, 5, 6, 7, 2, 3, 4, 5, 6, 7, etc. (repeats for each group of 6 digits) c = check digit Calculation (Step 1) m = sum of (d * w) for positions 1, 2, etc. starting with units digit for d = digit value starting with units position to highest order for w = weight value from 2 to 7 for every six positions starting with units digit (Step 2) c1 = m mod 11 (Step 3) if c1 = 0 then reset c1 = 1 (Step 4) = (11 - c1) mod 10 Example: If the number is 1234567, then the mod 11 check digit = 4 The calculations are: M = (7*2)+(6*3)+(5*4)+(4*5)+(3*6)+(2*7)+(1*2) = 14 + 18 + 20 + 20 + 18 + 14 + 2 = 106 c1 = 106 mod 11 = 7 c = (11-c1) mod 10 = 4 mod 10 = 4 Other variants of these check digit algorithms exist and may be used by local bilateral site agreement. Note: The check digit and code identifying check digit scheme are null if ID is alphanumeric. The assigning authority is a unique name of the system (or organization or agency or department) that creates the data. . Refer to User-defined Table 0363 – Assigning authority for suggested values. The reader is referred to the CX.9 and the CX.10 if there is a need to transmit values with semantic meaning for an assigning jurisdiction or assigning department or agency in addition to, or instead of, an assigning authority. However, all 3 components may be valued. If, in so doing, it is discovered that the values in CX.9 and/or CX.10 conflict with CX.4, the user would look to the Message Profile or other implementation agreement for a statement as to which takes precedence. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the patient. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component), may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The first date, if known, on which the identifier is valid and active. The last date, if known, on which the identifier is valid and active. The geo-political body that assigned the identifier in component 1. Refer to HL7 Table 0399 Country Code in section 2.15.9.17 for valid values if the administrative unit under whose jurisdiction the identifier was issued is a country. Refer to User-Defined Table 0347 State/Province for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a state or province. This table is country specific. In the US postal codes may be used. Refer to User-defined Table –0289 County/Parish for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a county or parish. The reader is referred to the CX.4, if there is a need to transmit this information as an OID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. Refer to User-defined Table –0530 Organizations, Agency, Department for suggested values if the administrative unit under whose jurisdiction the identifier was issued is an organization, agency or department. This is populated with site-specific assigning authorities. It also should contain national or international codes when CX-5 Identifier Type may be assigned by more than one authority within a governmental or organizational unit. For example, a federal government may have 2 departments that assign a military identifier, its Veterans Affairs department and its department of defense. It is not recommended to include values for entities such as Social Security Administration (SSA), Immigration and Naturalization Service (INS), Center for Medicare and Medicaid Services (CMS) because they are included in the identifier type table. In these cases the name of the country plus the identifier type yields the correct interpretation of the identifier in component one. Likewise, entries like department of motor vehicles (DMV) and licensing boards are not recommended for inclusion because the combination of state and identifier type yields the correct interpretation of the identifier in component one. This approach is not to be confused with the detailed information provided in the chapter 15 segments that have provision for specifying the precise granting body and issuing body information needed in personnel management messages. Example 1: <Identifier> plus <Visa> yields a unique identifier. Example 2: <Identifier> plus <state> plus <DLN> yields a unique driver’s license number. Example 3: <Identifier> plus <country> plus <INS> yields a unique immigration number. The reader is referred to the CX.4, if there is a need to transmit this information as an OID. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Insured's Group Emp Name The name of the specified organization. A code that represents the type of name i.e., legal name, display name. Refer to User-defined Table 0204 - Organizational Name Type for suggested values. This component has been retained for backward compatibility only as of v 2.5. It is recommended to use component 10 Organization identifier that accommodates alphanumeric identifiers. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. The check digit scheme codes are defined in HL7 Table 0061 - Check digit scheme. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Assigning authorities are unique across a given HL7 implementation. Refer to User-defined Table 0363 - Assigning Authority for suggested values. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e. even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation code for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component contains the sequence of characters (the code) that uniquely identifies the item being referenced by XON.1 Organization Name. This component replaces XON.3 ID Number as of v 2.5. Note: The check digit and code identifying check digit scheme are null if Organization identifier is alphanumeric. Ingangsdatum van de verzekering Einddatum van de verzekering Authorization Information Identifier assigned to the authorization. Date of authorization. Source of authorization. Soort verzekeringspakket. Hier wordt aangegeven of het om een Natura- ("N") of Restitutiepolis ("R") gaat. Naam van de (hoofd-)verzekerde, indien dit niet de patiënt zelf is. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, "FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. This component cannot be fully expressed. Identified as v 2.4 erratum. Retained for backward compatibility only as of v 2.5. Refer to Effective Date and Expiration Date components. This component contains the start and end date/times, which define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 0444 – Name assembly order for valid values. The first date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. Geboortedatum van de (hoofd-)verzekerde, indien dit niet de patiënt zelf is. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Geboortedatum van de (hoofd-)verzekerde, indien dit niet de patiënt zelf is. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Adres van de (hoofd-)verzekerde, indien dit niet de patiënt zelf is. Adres straat - Vanaf versie 2.4 is ‘street address’ een samengesteld datatype, waar in de verschillende onderdelen van het adres in verschillende subcomponenten kunnen worden opgenomen This component specifies the street or mailing address of a person or institution. When referencing an institution, this first component is used to specify the institution name. When used in connection with a person, this component specifies the first line of the address. Street Name Dwelling Number Huisnummertoevoeging Woonplaats Staat of provincie. Meestal niet relevant, maar gebruiken bij plaatsnamen in meerdere provincies zoals Afferden (Gelderland en Limburg) en Bergen (Noord-Holland en Limburg) Postcode, indien een Nederlandse postcode dan zonder spaties dus bijv. 2316XA. Merk op dat de HL7v3 specificatie met een spatie voorschrijft. Er is hier bewust gekozen voor compatibiliteit met de officiële HL7v2.4 NL specificatie. Land Adrestype. Voor het eerste adres moet deze de waarde ‘M’ (mailing) hebben. Andere adressen kunnen ook worden doorgegeven, zoals bijv. huisadres (‘H’), of tijdelijk/verblijfsadres (‘C’). Andere geografische aanduiding. N.v.t. voor Nederlandse adressen County/graafschap code. N.v.t. voor Nederlandse adressen Census tract. N.v.t. voor Nederlandse adressen. Representatiecode adres. N.v.t. voor Nederlandse adressen Adres geldigheidsperiode. Hierin kunnen eventueel de begin- en einddatum worden doorgegeven waarbinnen een adres geldig is. Dit kan bijv. voor tijdelijke adressen relevant zijn. Het is echter gemarkeerd als obsoleet en behouden voor backward compatbility in versie 2.5. Zie in plaats daarvan XAD.13 en XAD.14. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. Geldigheidsdatum. De eerste datum, indien bekend, waarop het adres geldig is/was en actief. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Verloopdatum. De laatste datum, indien bekend, waarop het adres geldig is/was en actief. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Assignment Of Benefits Coordination Of Benefits Coord Of Ben. Priority Notice Of Admission Flag Notice Of Admission Date Report Of Eligibility Flag Report Of Eligibility Date Release Information Code Pre-Admit Cert (PAC) Verification Date/Time The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Verification By This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Type Of Agreement Code Billing Status Lifetime Reserve Days Delay Before L.R. Day Company Plan Code Polisnummer van de patiënt bij de verzekeringsinstelling. Voor het inschrijfnummer van de patiënt bij de verzekeringsinstelling dient IN1-49 Insured’s ID Number gebruikt te worden. Policy Deductible The only required component; usually containing a decimal point. Note that each component of the MO data type (Section 2.A.41, "MO - money") is a subcomponent here. The first component is a quantity. The second component is the denomination in which the quantity is expressed. The values for the denomination component are those specified in ISO-4217. If the denomination is not specified, MSH-17-country code is used to determine the default. Example: |99.50^USD| where USD is the ISO 4217 code for the U.S. American dollar. A coded value, data type ID. Refer to HL7 Table 0205 - Price type for valid values. Each is a NM data type; together they specify the "range". The range can be defined as either time or quantity. For example, the range can indicate that the first 10 minutes of the procedure has one price. Another repetition of the data type can use the range to specify that the following 10 to 60 minutes of the procedure is charged at another price per; a final repetition can specify that the final 60 to N minutes of the procedure at a third price. Note that, if the <price type> component is TP, both <from value> and <to value> may be null. See <from value> above. A coded value, data type CE, defined by the standard table of units for either time or quantity (see for example, the tables in Section 7.1.4, "Coding schemes"). This describes the units associated with the range, e.g., seconds, minutes, hours, days, quantity (i.e., count); it is required if <from value> and <to value> are present. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Refer to HL7 Table 0298 - CP range type for valid values. Policy Limit - Amount The only required component; usually containing a decimal point. Note that each component of the MO data type (Section 2.A.41, "MO - money") is a subcomponent here. The first component is a quantity. The second component is the denomination in which the quantity is expressed. The values for the denomination component are those specified in ISO-4217. If the denomination is not specified, MSH-17-country code is used to determine the default. Example: |99.50^USD| where USD is the ISO 4217 code for the U.S. American dollar. A coded value, data type ID. Refer to HL7 Table 0205 - Price type for valid values. Each is a NM data type; together they specify the "range". The range can be defined as either time or quantity. For example, the range can indicate that the first 10 minutes of the procedure has one price. Another repetition of the data type can use the range to specify that the following 10 to 60 minutes of the procedure is charged at another price per; a final repetition can specify that the final 60 to N minutes of the procedure at a third price. Note that, if the <price type> component is TP, both <from value> and <to value> may be null. See <from value> above. A coded value, data type CE, defined by the standard table of units for either time or quantity (see for example, the tables in Section 7.1.4, "Coding schemes"). This describes the units associated with the range, e.g., seconds, minutes, hours, days, quantity (i.e., count); it is required if <from value> and <to value> are present. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Refer to HL7 Table 0298 - CP range type for valid values. Policy Limit - Days Room Rate - Semi-Private The only required component; usually containing a decimal point. Note that each component of the MO data type (Section 2.A.41, "MO - money") is a subcomponent here. The first component is a quantity. The second component is the denomination in which the quantity is expressed. The values for the denomination component are those specified in ISO-4217. If the denomination is not specified, MSH-17-country code is used to determine the default. Example: |99.50^USD| where USD is the ISO 4217 code for the U.S. American dollar. A coded value, data type ID. Refer to HL7 Table 0205 - Price type for valid values. Each is a NM data type; together they specify the "range". The range can be defined as either time or quantity. For example, the range can indicate that the first 10 minutes of the procedure has one price. Another repetition of the data type can use the range to specify that the following 10 to 60 minutes of the procedure is charged at another price per; a final repetition can specify that the final 60 to N minutes of the procedure at a third price. Note that, if the <price type> component is TP, both <from value> and <to value> may be null. See <from value> above. A coded value, data type CE, defined by the standard table of units for either time or quantity (see for example, the tables in Section 7.1.4, "Coding schemes"). This describes the units associated with the range, e.g., seconds, minutes, hours, days, quantity (i.e., count); it is required if <from value> and <to value> are present. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Refer to HL7 Table 0298 - CP range type for valid values. Room Rate - Private The only required component; usually containing a decimal point. Note that each component of the MO data type (Section 2.A.41, "MO - money") is a subcomponent here. The first component is a quantity. The second component is the denomination in which the quantity is expressed. The values for the denomination component are those specified in ISO-4217. If the denomination is not specified, MSH-17-country code is used to determine the default. Example: |99.50^USD| where USD is the ISO 4217 code for the U.S. American dollar. A coded value, data type ID. Refer to HL7 Table 0205 - Price type for valid values. Each is a NM data type; together they specify the "range". The range can be defined as either time or quantity. For example, the range can indicate that the first 10 minutes of the procedure has one price. Another repetition of the data type can use the range to specify that the following 10 to 60 minutes of the procedure is charged at another price per; a final repetition can specify that the final 60 to N minutes of the procedure at a third price. Note that, if the <price type> component is TP, both <from value> and <to value> may be null. See <from value> above. A coded value, data type CE, defined by the standard table of units for either time or quantity (see for example, the tables in Section 7.1.4, "Coding schemes"). This describes the units associated with the range, e.g., seconds, minutes, hours, days, quantity (i.e., count); it is required if <from value> and <to value> are present. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Refer to HL7 Table 0298 - CP range type for valid values. Insured's Employment Status Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Insured's Administrative Sex Insured's Employer's Address Adres straat - Vanaf versie 2.4 is ‘street address’ een samengesteld datatype, waar in de verschillende onderdelen van het adres in verschillende subcomponenten kunnen worden opgenomen This component specifies the street or mailing address of a person or institution. When referencing an institution, this first component is used to specify the institution name. When used in connection with a person, this component specifies the first line of the address. Street Name Dwelling Number Huisnummertoevoeging Woonplaats Staat of provincie. Meestal niet relevant, maar gebruiken bij plaatsnamen in meerdere provincies zoals Afferden (Gelderland en Limburg) en Bergen (Noord-Holland en Limburg) Postcode, indien een Nederlandse postcode dan zonder spaties dus bijv. 2316XA. Merk op dat de HL7v3 specificatie met een spatie voorschrijft. Er is hier bewust gekozen voor compatibiliteit met de officiële HL7v2.4 NL specificatie. Land Adrestype. Voor het eerste adres moet deze de waarde ‘M’ (mailing) hebben. Andere adressen kunnen ook worden doorgegeven, zoals bijv. huisadres (‘H’), of tijdelijk/verblijfsadres (‘C’). Andere geografische aanduiding. N.v.t. voor Nederlandse adressen County/graafschap code. N.v.t. voor Nederlandse adressen Census tract. N.v.t. voor Nederlandse adressen. Representatiecode adres. N.v.t. voor Nederlandse adressen Adres geldigheidsperiode. Hierin kunnen eventueel de begin- en einddatum worden doorgegeven waarbinnen een adres geldig is. Dit kan bijv. voor tijdelijke adressen relevant zijn. Het is echter gemarkeerd als obsoleet en behouden voor backward compatbility in versie 2.5. Zie in plaats daarvan XAD.13 en XAD.14. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. Geldigheidsdatum. De eerste datum, indien bekend, waarop het adres geldig is/was en actief. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Verloopdatum. De laatste datum, indien bekend, waarop het adres geldig is/was en actief. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Verification Status Prior Insurance Plan ID Coverage Type Handicap Inschrijfnummer van de patiënt bij de verzekeringsinstelling. Het polisnummer van de patiënt bij de verzekeringsinstelling staat in IN1-36. The value of the identifier itself. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. The algorithm for calculating a Mod10 check digit is as follows: Assume you have an identifier - 12345. Take the odd digit positions, counting from the right, i.e., 531, multiply this number by 2 to get 1062. Take the even digit positions, starting from the right (i.e., 42), prepend these to the 1062 to get 421062. Add all of these six digits together to get 15. Subtract this number from the next highest multiple of 10, i.e., 20 - 15 to get 5. The Mod10 check digit is 5. The Mod10 check digit for 401 is 0; for 9999, it’s 4; for 99999999, it’s 8. The algorithm for calculating a Mod11 check digit is as follows: Terms d = digit of number starting from units digit, followed by 10’s position, followed by 100’s position, etc. w = weight of digit position starting with the units position, followed by 10’s position, followed by 100’s position etc. Values for w = 2, 3, 4, 5, 6, 7, 2, 3, 4, 5, 6, 7, etc. (repeats for each group of 6 digits) c = check digit Calculation (Step 1) m = sum of (d * w) for positions 1, 2, etc. starting with units digit for d = digit value starting with units position to highest order for w = weight value from 2 to 7 for every six positions starting with units digit (Step 2) c1 = m mod 11 (Step 3) if c1 = 0 then reset c1 = 1 (Step 4) = (11 - c1) mod 10 Example: If the number is 1234567, then the mod 11 check digit = 4 The calculations are: M = (7*2)+(6*3)+(5*4)+(4*5)+(3*6)+(2*7)+(1*2) = 14 + 18 + 20 + 20 + 18 + 14 + 2 = 106 c1 = 106 mod 11 = 7 c = (11-c1) mod 10 = 4 mod 10 = 4 Other variants of these check digit algorithms exist and may be used by local bilateral site agreement. Note: The check digit and code identifying check digit scheme are null if ID is alphanumeric. The assigning authority is a unique name of the system (or organization or agency or department) that creates the data. . Refer to User-defined Table 0363 – Assigning authority for suggested values. The reader is referred to the CX.9 and the CX.10 if there is a need to transmit values with semantic meaning for an assigning jurisdiction or assigning department or agency in addition to, or instead of, an assigning authority. However, all 3 components may be valued. If, in so doing, it is discovered that the values in CX.9 and/or CX.10 conflict with CX.4, the user would look to the Message Profile or other implementation agreement for a statement as to which takes precedence. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the patient. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component), may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The first date, if known, on which the identifier is valid and active. The last date, if known, on which the identifier is valid and active. The geo-political body that assigned the identifier in component 1. Refer to HL7 Table 0399 Country Code in section 2.15.9.17 for valid values if the administrative unit under whose jurisdiction the identifier was issued is a country. Refer to User-Defined Table 0347 State/Province for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a state or province. This table is country specific. In the US postal codes may be used. Refer to User-defined Table –0289 County/Parish for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a county or parish. The reader is referred to the CX.4, if there is a need to transmit this information as an OID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. Refer to User-defined Table –0530 Organizations, Agency, Department for suggested values if the administrative unit under whose jurisdiction the identifier was issued is an organization, agency or department. This is populated with site-specific assigning authorities. It also should contain national or international codes when CX-5 Identifier Type may be assigned by more than one authority within a governmental or organizational unit. For example, a federal government may have 2 departments that assign a military identifier, its Veterans Affairs department and its department of defense. It is not recommended to include values for entities such as Social Security Administration (SSA), Immigration and Naturalization Service (INS), Center for Medicare and Medicaid Services (CMS) because they are included in the identifier type table. In these cases the name of the country plus the identifier type yields the correct interpretation of the identifier in component one. Likewise, entries like department of motor vehicles (DMV) and licensing boards are not recommended for inclusion because the combination of state and identifier type yields the correct interpretation of the identifier in component one. This approach is not to be confused with the detailed information provided in the chapter 15 segments that have provision for specifying the precise granting body and issuing body information needed in personnel management messages. Example 1: <Identifier> plus <Visa> yields a unique identifier. Example 2: <Identifier> plus <state> plus <DLN> yields a unique driver’s license number. Example 3: <Identifier> plus <country> plus <INS> yields a unique immigration number. The reader is referred to the CX.4, if there is a need to transmit this information as an OID. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Signature Code Signature Code Date Insured_s Birth Place VIP Indicator Insured's Employee ID The value of the identifier itself. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. The algorithm for calculating a Mod10 check digit is as follows: Assume you have an identifier - 12345. Take the odd digit positions, counting from the right, i.e., 531, multiply this number by 2 to get 1062. Take the even digit positions, starting from the right (i.e., 42), prepend these to the 1062 to get 421062. Add all of these six digits together to get 15. Subtract this number from the next highest multiple of 10, i.e., 20 - 15 to get 5. The Mod10 check digit is 5. The Mod10 check digit for 401 is 0; for 9999, it’s 4; for 99999999, it’s 8. The algorithm for calculating a Mod11 check digit is as follows: Terms d = digit of number starting from units digit, followed by 10’s position, followed by 100’s position, etc. w = weight of digit position starting with the units position, followed by 10’s position, followed by 100’s position etc. Values for w = 2, 3, 4, 5, 6, 7, 2, 3, 4, 5, 6, 7, etc. (repeats for each group of 6 digits) c = check digit Calculation (Step 1) m = sum of (d * w) for positions 1, 2, etc. starting with units digit for d = digit value starting with units position to highest order for w = weight value from 2 to 7 for every six positions starting with units digit (Step 2) c1 = m mod 11 (Step 3) if c1 = 0 then reset c1 = 1 (Step 4) = (11 - c1) mod 10 Example: If the number is 1234567, then the mod 11 check digit = 4 The calculations are: M = (7*2)+(6*3)+(5*4)+(4*5)+(3*6)+(2*7)+(1*2) = 14 + 18 + 20 + 20 + 18 + 14 + 2 = 106 c1 = 106 mod 11 = 7 c = (11-c1) mod 10 = 4 mod 10 = 4 Other variants of these check digit algorithms exist and may be used by local bilateral site agreement. Note: The check digit and code identifying check digit scheme are null if ID is alphanumeric. The assigning authority is a unique name of the system (or organization or agency or department) that creates the data. . Refer to User-defined Table 0363 – Assigning authority for suggested values. The reader is referred to the CX.9 and the CX.10 if there is a need to transmit values with semantic meaning for an assigning jurisdiction or assigning department or agency in addition to, or instead of, an assigning authority. However, all 3 components may be valued. If, in so doing, it is discovered that the values in CX.9 and/or CX.10 conflict with CX.4, the user would look to the Message Profile or other implementation agreement for a statement as to which takes precedence. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the patient. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component), may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The first date, if known, on which the identifier is valid and active. The last date, if known, on which the identifier is valid and active. The geo-political body that assigned the identifier in component 1. Refer to HL7 Table 0399 Country Code in section 2.15.9.17 for valid values if the administrative unit under whose jurisdiction the identifier was issued is a country. Refer to User-Defined Table 0347 State/Province for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a state or province. This table is country specific. In the US postal codes may be used. Refer to User-defined Table –0289 County/Parish for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a county or parish. The reader is referred to the CX.4, if there is a need to transmit this information as an OID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. Refer to User-defined Table –0530 Organizations, Agency, Department for suggested values if the administrative unit under whose jurisdiction the identifier was issued is an organization, agency or department. This is populated with site-specific assigning authorities. It also should contain national or international codes when CX-5 Identifier Type may be assigned by more than one authority within a governmental or organizational unit. For example, a federal government may have 2 departments that assign a military identifier, its Veterans Affairs department and its department of defense. It is not recommended to include values for entities such as Social Security Administration (SSA), Immigration and Naturalization Service (INS), Center for Medicare and Medicaid Services (CMS) because they are included in the identifier type table. In these cases the name of the country plus the identifier type yields the correct interpretation of the identifier in component one. Likewise, entries like department of motor vehicles (DMV) and licensing boards are not recommended for inclusion because the combination of state and identifier type yields the correct interpretation of the identifier in component one. This approach is not to be confused with the detailed information provided in the chapter 15 segments that have provision for specifying the precise granting body and issuing body information needed in personnel management messages. Example 1: <Identifier> plus <Visa> yields a unique identifier. Example 2: <Identifier> plus <state> plus <DLN> yields a unique driver’s license number. Example 3: <Identifier> plus <country> plus <INS> yields a unique immigration number. The reader is referred to the CX.4, if there is a need to transmit this information as an OID. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Insured's Social Security Number Insured's Employer's Name and ID This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Employer Information Data Mail Claim Party Medicare Health Ins Card Number Medicaid Case Name This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, "FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. This component cannot be fully expressed. Identified as v 2.4 erratum. Retained for backward compatibility only as of v 2.5. Refer to Effective Date and Expiration Date components. This component contains the start and end date/times, which define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 0444 – Name assembly order for valid values. The first date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. Medicaid Case Number Military Sponsor Name This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, "FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. This component cannot be fully expressed. Identified as v 2.4 erratum. Retained for backward compatibility only as of v 2.5. Refer to Effective Date and Expiration Date components. This component contains the start and end date/times, which define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 0444 – Name assembly order for valid values. The first date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. Military ID Number Dependent Of Military Recipient Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Military Organization Military Station Military Service Military Rank/Grade Military Status Military Retire Date Military Non-Avail Cert On File Baby Coverage Combine Baby Bill Blood Deductible Special Coverage Approval Name This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, "FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. This component cannot be fully expressed. Identified as v 2.4 erratum. Retained for backward compatibility only as of v 2.5. Refer to Effective Date and Expiration Date components. This component contains the start and end date/times, which define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 0444 – Name assembly order for valid values. The first date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. Special Coverage Approval Title Non-Covered Insurance Code Payor ID The value of the identifier itself. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. The algorithm for calculating a Mod10 check digit is as follows: Assume you have an identifier - 12345. Take the odd digit positions, counting from the right, i.e., 531, multiply this number by 2 to get 1062. Take the even digit positions, starting from the right (i.e., 42), prepend these to the 1062 to get 421062. Add all of these six digits together to get 15. Subtract this number from the next highest multiple of 10, i.e., 20 - 15 to get 5. The Mod10 check digit is 5. The Mod10 check digit for 401 is 0; for 9999, it’s 4; for 99999999, it’s 8. The algorithm for calculating a Mod11 check digit is as follows: Terms d = digit of number starting from units digit, followed by 10’s position, followed by 100’s position, etc. w = weight of digit position starting with the units position, followed by 10’s position, followed by 100’s position etc. Values for w = 2, 3, 4, 5, 6, 7, 2, 3, 4, 5, 6, 7, etc. (repeats for each group of 6 digits) c = check digit Calculation (Step 1) m = sum of (d * w) for positions 1, 2, etc. starting with units digit for d = digit value starting with units position to highest order for w = weight value from 2 to 7 for every six positions starting with units digit (Step 2) c1 = m mod 11 (Step 3) if c1 = 0 then reset c1 = 1 (Step 4) = (11 - c1) mod 10 Example: If the number is 1234567, then the mod 11 check digit = 4 The calculations are: M = (7*2)+(6*3)+(5*4)+(4*5)+(3*6)+(2*7)+(1*2) = 14 + 18 + 20 + 20 + 18 + 14 + 2 = 106 c1 = 106 mod 11 = 7 c = (11-c1) mod 10 = 4 mod 10 = 4 Other variants of these check digit algorithms exist and may be used by local bilateral site agreement. Note: The check digit and code identifying check digit scheme are null if ID is alphanumeric. The assigning authority is a unique name of the system (or organization or agency or department) that creates the data. . Refer to User-defined Table 0363 – Assigning authority for suggested values. The reader is referred to the CX.9 and the CX.10 if there is a need to transmit values with semantic meaning for an assigning jurisdiction or assigning department or agency in addition to, or instead of, an assigning authority. However, all 3 components may be valued. If, in so doing, it is discovered that the values in CX.9 and/or CX.10 conflict with CX.4, the user would look to the Message Profile or other implementation agreement for a statement as to which takes precedence. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the patient. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component), may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The first date, if known, on which the identifier is valid and active. The last date, if known, on which the identifier is valid and active. The geo-political body that assigned the identifier in component 1. Refer to HL7 Table 0399 Country Code in section 2.15.9.17 for valid values if the administrative unit under whose jurisdiction the identifier was issued is a country. Refer to User-Defined Table 0347 State/Province for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a state or province. This table is country specific. In the US postal codes may be used. Refer to User-defined Table –0289 County/Parish for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a county or parish. The reader is referred to the CX.4, if there is a need to transmit this information as an OID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. Refer to User-defined Table –0530 Organizations, Agency, Department for suggested values if the administrative unit under whose jurisdiction the identifier was issued is an organization, agency or department. This is populated with site-specific assigning authorities. It also should contain national or international codes when CX-5 Identifier Type may be assigned by more than one authority within a governmental or organizational unit. For example, a federal government may have 2 departments that assign a military identifier, its Veterans Affairs department and its department of defense. It is not recommended to include values for entities such as Social Security Administration (SSA), Immigration and Naturalization Service (INS), Center for Medicare and Medicaid Services (CMS) because they are included in the identifier type table. In these cases the name of the country plus the identifier type yields the correct interpretation of the identifier in component one. Likewise, entries like department of motor vehicles (DMV) and licensing boards are not recommended for inclusion because the combination of state and identifier type yields the correct interpretation of the identifier in component one. This approach is not to be confused with the detailed information provided in the chapter 15 segments that have provision for specifying the precise granting body and issuing body information needed in personnel management messages. Example 1: <Identifier> plus <Visa> yields a unique identifier. Example 2: <Identifier> plus <state> plus <DLN> yields a unique driver’s license number. Example 3: <Identifier> plus <country> plus <INS> yields a unique immigration number. The reader is referred to the CX.4, if there is a need to transmit this information as an OID. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Payor Subscriber ID The value of the identifier itself. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. The algorithm for calculating a Mod10 check digit is as follows: Assume you have an identifier - 12345. Take the odd digit positions, counting from the right, i.e., 531, multiply this number by 2 to get 1062. Take the even digit positions, starting from the right (i.e., 42), prepend these to the 1062 to get 421062. Add all of these six digits together to get 15. Subtract this number from the next highest multiple of 10, i.e., 20 - 15 to get 5. The Mod10 check digit is 5. The Mod10 check digit for 401 is 0; for 9999, it’s 4; for 99999999, it’s 8. The algorithm for calculating a Mod11 check digit is as follows: Terms d = digit of number starting from units digit, followed by 10’s position, followed by 100’s position, etc. w = weight of digit position starting with the units position, followed by 10’s position, followed by 100’s position etc. Values for w = 2, 3, 4, 5, 6, 7, 2, 3, 4, 5, 6, 7, etc. (repeats for each group of 6 digits) c = check digit Calculation (Step 1) m = sum of (d * w) for positions 1, 2, etc. starting with units digit for d = digit value starting with units position to highest order for w = weight value from 2 to 7 for every six positions starting with units digit (Step 2) c1 = m mod 11 (Step 3) if c1 = 0 then reset c1 = 1 (Step 4) = (11 - c1) mod 10 Example: If the number is 1234567, then the mod 11 check digit = 4 The calculations are: M = (7*2)+(6*3)+(5*4)+(4*5)+(3*6)+(2*7)+(1*2) = 14 + 18 + 20 + 20 + 18 + 14 + 2 = 106 c1 = 106 mod 11 = 7 c = (11-c1) mod 10 = 4 mod 10 = 4 Other variants of these check digit algorithms exist and may be used by local bilateral site agreement. Note: The check digit and code identifying check digit scheme are null if ID is alphanumeric. The assigning authority is a unique name of the system (or organization or agency or department) that creates the data. . Refer to User-defined Table 0363 – Assigning authority for suggested values. The reader is referred to the CX.9 and the CX.10 if there is a need to transmit values with semantic meaning for an assigning jurisdiction or assigning department or agency in addition to, or instead of, an assigning authority. However, all 3 components may be valued. If, in so doing, it is discovered that the values in CX.9 and/or CX.10 conflict with CX.4, the user would look to the Message Profile or other implementation agreement for a statement as to which takes precedence. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the patient. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component), may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The first date, if known, on which the identifier is valid and active. The last date, if known, on which the identifier is valid and active. The geo-political body that assigned the identifier in component 1. Refer to HL7 Table 0399 Country Code in section 2.15.9.17 for valid values if the administrative unit under whose jurisdiction the identifier was issued is a country. Refer to User-Defined Table 0347 State/Province for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a state or province. This table is country specific. In the US postal codes may be used. Refer to User-defined Table –0289 County/Parish for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a county or parish. The reader is referred to the CX.4, if there is a need to transmit this information as an OID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. Refer to User-defined Table –0530 Organizations, Agency, Department for suggested values if the administrative unit under whose jurisdiction the identifier was issued is an organization, agency or department. This is populated with site-specific assigning authorities. It also should contain national or international codes when CX-5 Identifier Type may be assigned by more than one authority within a governmental or organizational unit. For example, a federal government may have 2 departments that assign a military identifier, its Veterans Affairs department and its department of defense. It is not recommended to include values for entities such as Social Security Administration (SSA), Immigration and Naturalization Service (INS), Center for Medicare and Medicaid Services (CMS) because they are included in the identifier type table. In these cases the name of the country plus the identifier type yields the correct interpretation of the identifier in component one. Likewise, entries like department of motor vehicles (DMV) and licensing boards are not recommended for inclusion because the combination of state and identifier type yields the correct interpretation of the identifier in component one. This approach is not to be confused with the detailed information provided in the chapter 15 segments that have provision for specifying the precise granting body and issuing body information needed in personnel management messages. Example 1: <Identifier> plus <Visa> yields a unique identifier. Example 2: <Identifier> plus <state> plus <DLN> yields a unique driver’s license number. Example 3: <Identifier> plus <country> plus <INS> yields a unique immigration number. The reader is referred to the CX.4, if there is a need to transmit this information as an OID. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Eligibility Source Room Coverage Type/Amount Specifies the room type. Refer to User-defined Table 0145 - Room type for suggested values. Specifies amount quantity type Refer to User-defined Table 0146 - Amount type for suggested values. Specifies amount covered by the insurance as a currency or percentage quantity. Retained for backward compatibility only as of v 2.5. Refer to 2.9.69.4 – Money or Percentage. Specifies an amount that may be either currency or a percentage. Specifies whether the amount is currency or a percentage. Refer to HL7 Table 0148 – Money or percentage indicator for valid values. Specifies the currency or percentage quantity. the denomination in which the quantity is expressed where the amount is currency. The values for the denomination component are those specified in ISO-4217. If the denomination is not specified, the context of the message or MSH-17-country code is used to determine the default. Policy Type/Amount Specifies the policy type. Refer to User-defined Table 0147 - Policy type for suggested values. Specifies the amount quantity class. Refer to User-defined Table 0193 - Amount class for suggested values. Specifies the currency or percentage quantity. Retained for backward compatibility only as of v 2.5. Refer to PTA.4 instead. Specifies an amount that may be either currency or a percentage. Specifies whether the amount is currency or a percentage. Refer to HL7 Table 0148 – Money or percentage indicator for valid values. Specifies the currency or percentage quantity. the denomination in which the quantity is expressed where the amount is currency. The values for the denomination component are those specified in ISO-4217. If the denomination is not specified, the context of the message or MSH-17-country code is used to determine the default. Daily Deductible The number of days after which the daily deductible begins The monetary amount of the deductible The first component is a quantity. The second component is the denomination in which the quantity is expressed. The values for the denomination component are those specified in ISO-4217. If the denomination is not specified, MSH-17-country code is used to determine the default. Example: |99.50^USD| where USD is the ISO 4217 code for the U.S. American dollar. The number of days to apply the deductible. If this component is not populated, it means that the number of days is indefinite. Living Dependency Ambulatory Status Citizenship Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Primary Language Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Living Arrangement Publicity Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Protection Indicator Student Indicator Religion Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Mother's Maiden Name This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, "FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. This component cannot be fully expressed. Identified as v 2.4 erratum. Retained for backward compatibility only as of v 2.5. Refer to Effective Date and Expiration Date components. This component contains the start and end date/times, which define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 0444 – Name assembly order for valid values. The first date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. Nationality Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Ethnic Group Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Marital Status Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Insured's Employment Start Date Employment Stop Date Job Title Job Code/Class This component contains the person’s job code. User-defined Table 0327 - Job code is used as the HL7 identifier for the user-defined table of values for this component. This component contains the person’s employee classification. Refer to User-defined Table 0328 - Employee classification for suggested values. This component contains the text of the job description. This will accommodate systems where job descriptions are not codified. Job Status Employer Contact Person Name This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, "FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. This component cannot be fully expressed. Identified as v 2.4 erratum. Retained for backward compatibility only as of v 2.5. Refer to Effective Date and Expiration Date components. This component contains the start and end date/times, which define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 0444 – Name assembly order for valid values. The first date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. Employer Contact Person Phone Number Specifies the telephone number in a predetermined format that includes an optional extension, beeper number and comment. This component has been retained for backward compatibility only as of version 2.3. Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C any text] Note: Because this component has been deprecated a new data type has not been defined to replace the formatted ST. A code that represents a specific use of a telecommunication number. Refer to HL7 Table 0201 - Telecommunication use code for valid values. A code that represents the type of telecommunication equipment. Refer to HL7 Table 0202 - Telecommunication equipment type for valid values. Internationalization note: To make this data type interoperate with CEN’s Telecommunication data attribute group, we allow use of the second component for email addresses. The presence of an email address is specified by the addition of the value NET to the Phone Use Code table, and the type of Internet address is specified with the values Internet and X.400 to the Phone Equipment Type table. When used for an Internet address, the first component of the XTN data type will be null. If the @-sign is being used as a subcomponent delimiter, the HL7 subcomponent escape sequence may be used when encoding an Internet address (see Section Country Code (NM). Country Code Area/City Code Local Number Extension Contains comments with respect to the telephone number. The characters established within a company’s internal telephone system network used as a prefix to the Extension component for internal dialing. Note that the use of Extension Prefix requires that the Extension component be valued and that digits, as well as special characters (e.g., *, #) may be used. The characters established within a company’s internal telephone system used in place of the (external) telephone number to facilitate calling because its length is shorter than that of the telephone number. Note that digits, as well as special characters (e.g., *, #) may be used. An expression of the telephone number as an unparsible string. The phone number was entered as free text and sending system does not know how to parse it. Employer Contact Reason Insured's Contact Person's Name This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, "FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. This component cannot be fully expressed. Identified as v 2.4 erratum. Retained for backward compatibility only as of v 2.5. Refer to Effective Date and Expiration Date components. This component contains the start and end date/times, which define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 0444 – Name assembly order for valid values. The first date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. Insured's Contact Person Phone Number Specifies the telephone number in a predetermined format that includes an optional extension, beeper number and comment. This component has been retained for backward compatibility only as of version 2.3. Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C any text] Note: Because this component has been deprecated a new data type has not been defined to replace the formatted ST. A code that represents a specific use of a telecommunication number. Refer to HL7 Table 0201 - Telecommunication use code for valid values. A code that represents the type of telecommunication equipment. Refer to HL7 Table 0202 - Telecommunication equipment type for valid values. Internationalization note: To make this data type interoperate with CEN’s Telecommunication data attribute group, we allow use of the second component for email addresses. The presence of an email address is specified by the addition of the value NET to the Phone Use Code table, and the type of Internet address is specified with the values Internet and X.400 to the Phone Equipment Type table. When used for an Internet address, the first component of the XTN data type will be null. If the @-sign is being used as a subcomponent delimiter, the HL7 subcomponent escape sequence may be used when encoding an Internet address (see Section Country Code (NM). Country Code Area/City Code Local Number Extension Contains comments with respect to the telephone number. The characters established within a company’s internal telephone system network used as a prefix to the Extension component for internal dialing. Note that the use of Extension Prefix requires that the Extension component be valued and that digits, as well as special characters (e.g., *, #) may be used. The characters established within a company’s internal telephone system used in place of the (external) telephone number to facilitate calling because its length is shorter than that of the telephone number. Note that digits, as well as special characters (e.g., *, #) may be used. An expression of the telephone number as an unparsible string. The phone number was entered as free text and sending system does not know how to parse it. Insured's Contact Person Reason Relationship to the Patient Start Date Relationship to the Patient Stop Date Insurance Co. Contact Reason Insurance Co Contact Phone Number Specifies the telephone number in a predetermined format that includes an optional extension, beeper number and comment. This component has been retained for backward compatibility only as of version 2.3. Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C any text] Note: Because this component has been deprecated a new data type has not been defined to replace the formatted ST. A code that represents a specific use of a telecommunication number. Refer to HL7 Table 0201 - Telecommunication use code for valid values. A code that represents the type of telecommunication equipment. Refer to HL7 Table 0202 - Telecommunication equipment type for valid values. Internationalization note: To make this data type interoperate with CEN’s Telecommunication data attribute group, we allow use of the second component for email addresses. The presence of an email address is specified by the addition of the value NET to the Phone Use Code table, and the type of Internet address is specified with the values Internet and X.400 to the Phone Equipment Type table. When used for an Internet address, the first component of the XTN data type will be null. If the @-sign is being used as a subcomponent delimiter, the HL7 subcomponent escape sequence may be used when encoding an Internet address (see Section Country Code (NM). Country Code Area/City Code Local Number Extension Contains comments with respect to the telephone number. The characters established within a company’s internal telephone system network used as a prefix to the Extension component for internal dialing. Note that the use of Extension Prefix requires that the Extension component be valued and that digits, as well as special characters (e.g., *, #) may be used. The characters established within a company’s internal telephone system used in place of the (external) telephone number to facilitate calling because its length is shorter than that of the telephone number. Note that digits, as well as special characters (e.g., *, #) may be used. An expression of the telephone number as an unparsible string. The phone number was entered as free text and sending system does not know how to parse it. Policy Scope Policy Source Patient Member Number The value of the identifier itself. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. The algorithm for calculating a Mod10 check digit is as follows: Assume you have an identifier - 12345. Take the odd digit positions, counting from the right, i.e., 531, multiply this number by 2 to get 1062. Take the even digit positions, starting from the right (i.e., 42), prepend these to the 1062 to get 421062. Add all of these six digits together to get 15. Subtract this number from the next highest multiple of 10, i.e., 20 - 15 to get 5. The Mod10 check digit is 5. The Mod10 check digit for 401 is 0; for 9999, it’s 4; for 99999999, it’s 8. The algorithm for calculating a Mod11 check digit is as follows: Terms d = digit of number starting from units digit, followed by 10’s position, followed by 100’s position, etc. w = weight of digit position starting with the units position, followed by 10’s position, followed by 100’s position etc. Values for w = 2, 3, 4, 5, 6, 7, 2, 3, 4, 5, 6, 7, etc. (repeats for each group of 6 digits) c = check digit Calculation (Step 1) m = sum of (d * w) for positions 1, 2, etc. starting with units digit for d = digit value starting with units position to highest order for w = weight value from 2 to 7 for every six positions starting with units digit (Step 2) c1 = m mod 11 (Step 3) if c1 = 0 then reset c1 = 1 (Step 4) = (11 - c1) mod 10 Example: If the number is 1234567, then the mod 11 check digit = 4 The calculations are: M = (7*2)+(6*3)+(5*4)+(4*5)+(3*6)+(2*7)+(1*2) = 14 + 18 + 20 + 20 + 18 + 14 + 2 = 106 c1 = 106 mod 11 = 7 c = (11-c1) mod 10 = 4 mod 10 = 4 Other variants of these check digit algorithms exist and may be used by local bilateral site agreement. Note: The check digit and code identifying check digit scheme are null if ID is alphanumeric. The assigning authority is a unique name of the system (or organization or agency or department) that creates the data. . Refer to User-defined Table 0363 – Assigning authority for suggested values. The reader is referred to the CX.9 and the CX.10 if there is a need to transmit values with semantic meaning for an assigning jurisdiction or assigning department or agency in addition to, or instead of, an assigning authority. However, all 3 components may be valued. If, in so doing, it is discovered that the values in CX.9 and/or CX.10 conflict with CX.4, the user would look to the Message Profile or other implementation agreement for a statement as to which takes precedence. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the patient. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component), may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The first date, if known, on which the identifier is valid and active. The last date, if known, on which the identifier is valid and active. The geo-political body that assigned the identifier in component 1. Refer to HL7 Table 0399 Country Code in section 2.15.9.17 for valid values if the administrative unit under whose jurisdiction the identifier was issued is a country. Refer to User-Defined Table 0347 State/Province for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a state or province. This table is country specific. In the US postal codes may be used. Refer to User-defined Table –0289 County/Parish for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a county or parish. The reader is referred to the CX.4, if there is a need to transmit this information as an OID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. Refer to User-defined Table –0530 Organizations, Agency, Department for suggested values if the administrative unit under whose jurisdiction the identifier was issued is an organization, agency or department. This is populated with site-specific assigning authorities. It also should contain national or international codes when CX-5 Identifier Type may be assigned by more than one authority within a governmental or organizational unit. For example, a federal government may have 2 departments that assign a military identifier, its Veterans Affairs department and its department of defense. It is not recommended to include values for entities such as Social Security Administration (SSA), Immigration and Naturalization Service (INS), Center for Medicare and Medicaid Services (CMS) because they are included in the identifier type table. In these cases the name of the country plus the identifier type yields the correct interpretation of the identifier in component one. Likewise, entries like department of motor vehicles (DMV) and licensing boards are not recommended for inclusion because the combination of state and identifier type yields the correct interpretation of the identifier in component one. This approach is not to be confused with the detailed information provided in the chapter 15 segments that have provision for specifying the precise granting body and issuing body information needed in personnel management messages. Example 1: <Identifier> plus <Visa> yields a unique identifier. Example 2: <Identifier> plus <state> plus <DLN> yields a unique driver’s license number. Example 3: <Identifier> plus <country> plus <INS> yields a unique immigration number. The reader is referred to the CX.4, if there is a need to transmit this information as an OID. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Guarantor's Relationship To Insured Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Insured's Phone Number - Home Specifies the telephone number in a predetermined format that includes an optional extension, beeper number and comment. This component has been retained for backward compatibility only as of version 2.3. Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C any text] Note: Because this component has been deprecated a new data type has not been defined to replace the formatted ST. A code that represents a specific use of a telecommunication number. Refer to HL7 Table 0201 - Telecommunication use code for valid values. A code that represents the type of telecommunication equipment. Refer to HL7 Table 0202 - Telecommunication equipment type for valid values. Internationalization note: To make this data type interoperate with CEN’s Telecommunication data attribute group, we allow use of the second component for email addresses. The presence of an email address is specified by the addition of the value NET to the Phone Use Code table, and the type of Internet address is specified with the values Internet and X.400 to the Phone Equipment Type table. When used for an Internet address, the first component of the XTN data type will be null. If the @-sign is being used as a subcomponent delimiter, the HL7 subcomponent escape sequence may be used when encoding an Internet address (see Section Country Code (NM). Country Code Area/City Code Local Number Extension Contains comments with respect to the telephone number. The characters established within a company’s internal telephone system network used as a prefix to the Extension component for internal dialing. Note that the use of Extension Prefix requires that the Extension component be valued and that digits, as well as special characters (e.g., *, #) may be used. The characters established within a company’s internal telephone system used in place of the (external) telephone number to facilitate calling because its length is shorter than that of the telephone number. Note that digits, as well as special characters (e.g., *, #) may be used. An expression of the telephone number as an unparsible string. The phone number was entered as free text and sending system does not know how to parse it. Insured's Employer Phone Number Specifies the telephone number in a predetermined format that includes an optional extension, beeper number and comment. This component has been retained for backward compatibility only as of version 2.3. Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C any text] Note: Because this component has been deprecated a new data type has not been defined to replace the formatted ST. A code that represents a specific use of a telecommunication number. Refer to HL7 Table 0201 - Telecommunication use code for valid values. A code that represents the type of telecommunication equipment. Refer to HL7 Table 0202 - Telecommunication equipment type for valid values. Internationalization note: To make this data type interoperate with CEN’s Telecommunication data attribute group, we allow use of the second component for email addresses. The presence of an email address is specified by the addition of the value NET to the Phone Use Code table, and the type of Internet address is specified with the values Internet and X.400 to the Phone Equipment Type table. When used for an Internet address, the first component of the XTN data type will be null. If the @-sign is being used as a subcomponent delimiter, the HL7 subcomponent escape sequence may be used when encoding an Internet address (see Section Country Code (NM). Country Code Area/City Code Local Number Extension Contains comments with respect to the telephone number. The characters established within a company’s internal telephone system network used as a prefix to the Extension component for internal dialing. Note that the use of Extension Prefix requires that the Extension component be valued and that digits, as well as special characters (e.g., *, #) may be used. The characters established within a company’s internal telephone system used in place of the (external) telephone number to facilitate calling because its length is shorter than that of the telephone number. Note that digits, as well as special characters (e.g., *, #) may be used. An expression of the telephone number as an unparsible string. The phone number was entered as free text and sending system does not know how to parse it. Military Handicapped Program Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Suspend Flag Copay Limit Flag Stoploss Limit Flag Insured Organization Name and ID The name of the specified organization. A code that represents the type of name i.e., legal name, display name. Refer to User-defined Table 0204 - Organizational Name Type for suggested values. This component has been retained for backward compatibility only as of v 2.5. It is recommended to use component 10 Organization identifier that accommodates alphanumeric identifiers. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. The check digit scheme codes are defined in HL7 Table 0061 - Check digit scheme. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Assigning authorities are unique across a given HL7 implementation. Refer to User-defined Table 0363 - Assigning Authority for suggested values. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e. even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation code for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component contains the sequence of characters (the code) that uniquely identifies the item being referenced by XON.1 Organization Name. This component replaces XON.3 ID Number as of v 2.5. Note: The check digit and code identifying check digit scheme are null if Organization identifier is alphanumeric. Insured Employer Organization Name and ID The name of the specified organization. A code that represents the type of name i.e., legal name, display name. Refer to User-defined Table 0204 - Organizational Name Type for suggested values. This component has been retained for backward compatibility only as of v 2.5. It is recommended to use component 10 Organization identifier that accommodates alphanumeric identifiers. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. The check digit scheme codes are defined in HL7 Table 0061 - Check digit scheme. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Assigning authorities are unique across a given HL7 implementation. Refer to User-defined Table 0363 - Assigning Authority for suggested values. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e. even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation code for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component contains the sequence of characters (the code) that uniquely identifies the item being referenced by XON.1 Organization Name. This component replaces XON.3 ID Number as of v 2.5. Note: The check digit and code identifying check digit scheme are null if Organization identifier is alphanumeric. Race Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. CMS Patient_s Relationship to Insured Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Set ID - IN3 Certification Number The value of the identifier itself. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. The algorithm for calculating a Mod10 check digit is as follows: Assume you have an identifier - 12345. Take the odd digit positions, counting from the right, i.e., 531, multiply this number by 2 to get 1062. Take the even digit positions, starting from the right (i.e., 42), prepend these to the 1062 to get 421062. Add all of these six digits together to get 15. Subtract this number from the next highest multiple of 10, i.e., 20 - 15 to get 5. The Mod10 check digit is 5. The Mod10 check digit for 401 is 0; for 9999, it’s 4; for 99999999, it’s 8. The algorithm for calculating a Mod11 check digit is as follows: Terms d = digit of number starting from units digit, followed by 10’s position, followed by 100’s position, etc. w = weight of digit position starting with the units position, followed by 10’s position, followed by 100’s position etc. Values for w = 2, 3, 4, 5, 6, 7, 2, 3, 4, 5, 6, 7, etc. (repeats for each group of 6 digits) c = check digit Calculation (Step 1) m = sum of (d * w) for positions 1, 2, etc. starting with units digit for d = digit value starting with units position to highest order for w = weight value from 2 to 7 for every six positions starting with units digit (Step 2) c1 = m mod 11 (Step 3) if c1 = 0 then reset c1 = 1 (Step 4) = (11 - c1) mod 10 Example: If the number is 1234567, then the mod 11 check digit = 4 The calculations are: M = (7*2)+(6*3)+(5*4)+(4*5)+(3*6)+(2*7)+(1*2) = 14 + 18 + 20 + 20 + 18 + 14 + 2 = 106 c1 = 106 mod 11 = 7 c = (11-c1) mod 10 = 4 mod 10 = 4 Other variants of these check digit algorithms exist and may be used by local bilateral site agreement. Note: The check digit and code identifying check digit scheme are null if ID is alphanumeric. The assigning authority is a unique name of the system (or organization or agency or department) that creates the data. . Refer to User-defined Table 0363 – Assigning authority for suggested values. The reader is referred to the CX.9 and the CX.10 if there is a need to transmit values with semantic meaning for an assigning jurisdiction or assigning department or agency in addition to, or instead of, an assigning authority. However, all 3 components may be valued. If, in so doing, it is discovered that the values in CX.9 and/or CX.10 conflict with CX.4, the user would look to the Message Profile or other implementation agreement for a statement as to which takes precedence. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the patient. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component), may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The first date, if known, on which the identifier is valid and active. The last date, if known, on which the identifier is valid and active. The geo-political body that assigned the identifier in component 1. Refer to HL7 Table 0399 Country Code in section 2.15.9.17 for valid values if the administrative unit under whose jurisdiction the identifier was issued is a country. Refer to User-Defined Table 0347 State/Province for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a state or province. This table is country specific. In the US postal codes may be used. Refer to User-defined Table –0289 County/Parish for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a county or parish. The reader is referred to the CX.4, if there is a need to transmit this information as an OID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. Refer to User-defined Table –0530 Organizations, Agency, Department for suggested values if the administrative unit under whose jurisdiction the identifier was issued is an organization, agency or department. This is populated with site-specific assigning authorities. It also should contain national or international codes when CX-5 Identifier Type may be assigned by more than one authority within a governmental or organizational unit. For example, a federal government may have 2 departments that assign a military identifier, its Veterans Affairs department and its department of defense. It is not recommended to include values for entities such as Social Security Administration (SSA), Immigration and Naturalization Service (INS), Center for Medicare and Medicaid Services (CMS) because they are included in the identifier type table. In these cases the name of the country plus the identifier type yields the correct interpretation of the identifier in component one. Likewise, entries like department of motor vehicles (DMV) and licensing boards are not recommended for inclusion because the combination of state and identifier type yields the correct interpretation of the identifier in component one. This approach is not to be confused with the detailed information provided in the chapter 15 segments that have provision for specifying the precise granting body and issuing body information needed in personnel management messages. Example 1: <Identifier> plus <Visa> yields a unique identifier. Example 2: <Identifier> plus <state> plus <DLN> yields a unique driver’s license number. Example 3: <Identifier> plus <country> plus <INS> yields a unique immigration number. The reader is referred to the CX.4, if there is a need to transmit this information as an OID. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Certified By This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Certification Required Penalty Specifies whether the amount is currency or a percentage. Refer to HL7 Table 0148 – Money or percentage indicator for valid values. Specifies the currency or percentage quantity. the denomination in which the quantity is expressed where the amount is currency. The values for the denomination component are those specified in ISO-4217. If the denomination is not specified, the context of the message or MSH-17-country code is used to determine the default. Certification Date/Time The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Certification Modify Date/Time The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Operator This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Certification Begin Date Certification End Date Days Specifies whether the days are denied, pending, or approved. Refer to User-defined Table 0149 - Day type for suggested values. Specifies the number of days for which the certification is valid. Non-Concur Code/Description Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Non-Concur Effective Date/Time The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Physician Reviewer This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Certification Contact Certification Contact Phone Number Specifies the telephone number in a predetermined format that includes an optional extension, beeper number and comment. This component has been retained for backward compatibility only as of version 2.3. Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C any text] Note: Because this component has been deprecated a new data type has not been defined to replace the formatted ST. A code that represents a specific use of a telecommunication number. Refer to HL7 Table 0201 - Telecommunication use code for valid values. A code that represents the type of telecommunication equipment. Refer to HL7 Table 0202 - Telecommunication equipment type for valid values. Internationalization note: To make this data type interoperate with CEN’s Telecommunication data attribute group, we allow use of the second component for email addresses. The presence of an email address is specified by the addition of the value NET to the Phone Use Code table, and the type of Internet address is specified with the values Internet and X.400 to the Phone Equipment Type table. When used for an Internet address, the first component of the XTN data type will be null. If the @-sign is being used as a subcomponent delimiter, the HL7 subcomponent escape sequence may be used when encoding an Internet address (see Section Country Code (NM). Country Code Area/City Code Local Number Extension Contains comments with respect to the telephone number. The characters established within a company’s internal telephone system network used as a prefix to the Extension component for internal dialing. Note that the use of Extension Prefix requires that the Extension component be valued and that digits, as well as special characters (e.g., *, #) may be used. The characters established within a company’s internal telephone system used in place of the (external) telephone number to facilitate calling because its length is shorter than that of the telephone number. Note that digits, as well as special characters (e.g., *, #) may be used. An expression of the telephone number as an unparsible string. The phone number was entered as free text and sending system does not know how to parse it. Appeal Reason Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Certification Agency Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Certification Agency Phone Number Specifies the telephone number in a predetermined format that includes an optional extension, beeper number and comment. This component has been retained for backward compatibility only as of version 2.3. Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C any text] Note: Because this component has been deprecated a new data type has not been defined to replace the formatted ST. A code that represents a specific use of a telecommunication number. Refer to HL7 Table 0201 - Telecommunication use code for valid values. A code that represents the type of telecommunication equipment. Refer to HL7 Table 0202 - Telecommunication equipment type for valid values. Internationalization note: To make this data type interoperate with CEN’s Telecommunication data attribute group, we allow use of the second component for email addresses. The presence of an email address is specified by the addition of the value NET to the Phone Use Code table, and the type of Internet address is specified with the values Internet and X.400 to the Phone Equipment Type table. When used for an Internet address, the first component of the XTN data type will be null. If the @-sign is being used as a subcomponent delimiter, the HL7 subcomponent escape sequence may be used when encoding an Internet address (see Section Country Code (NM). Country Code Area/City Code Local Number Extension Contains comments with respect to the telephone number. The characters established within a company’s internal telephone system network used as a prefix to the Extension component for internal dialing. Note that the use of Extension Prefix requires that the Extension component be valued and that digits, as well as special characters (e.g., *, #) may be used. The characters established within a company’s internal telephone system used in place of the (external) telephone number to facilitate calling because its length is shorter than that of the telephone number. Note that digits, as well as special characters (e.g., *, #) may be used. An expression of the telephone number as an unparsible string. The phone number was entered as free text and sending system does not know how to parse it. Pre-Certification Requirement Specifies the category or type of patient for which this certification is requested. Refer to User-defined Table 0150 - Certification patient type for suggested values. Specifies whether or not a certification is required. Refer to HL7 table 0136 - Yes/no indicator for valid values. The date/time by which the certification must be obtained. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Case Manager Second Opinion Date Second Opinion Status Second Opinion Documentation Received Second Opinion Physician This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Set ID - GT1 Guarantor Number The value of the identifier itself. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. The algorithm for calculating a Mod10 check digit is as follows: Assume you have an identifier - 12345. Take the odd digit positions, counting from the right, i.e., 531, multiply this number by 2 to get 1062. Take the even digit positions, starting from the right (i.e., 42), prepend these to the 1062 to get 421062. Add all of these six digits together to get 15. Subtract this number from the next highest multiple of 10, i.e., 20 - 15 to get 5. The Mod10 check digit is 5. The Mod10 check digit for 401 is 0; for 9999, it’s 4; for 99999999, it’s 8. The algorithm for calculating a Mod11 check digit is as follows: Terms d = digit of number starting from units digit, followed by 10’s position, followed by 100’s position, etc. w = weight of digit position starting with the units position, followed by 10’s position, followed by 100’s position etc. Values for w = 2, 3, 4, 5, 6, 7, 2, 3, 4, 5, 6, 7, etc. (repeats for each group of 6 digits) c = check digit Calculation (Step 1) m = sum of (d * w) for positions 1, 2, etc. starting with units digit for d = digit value starting with units position to highest order for w = weight value from 2 to 7 for every six positions starting with units digit (Step 2) c1 = m mod 11 (Step 3) if c1 = 0 then reset c1 = 1 (Step 4) = (11 - c1) mod 10 Example: If the number is 1234567, then the mod 11 check digit = 4 The calculations are: M = (7*2)+(6*3)+(5*4)+(4*5)+(3*6)+(2*7)+(1*2) = 14 + 18 + 20 + 20 + 18 + 14 + 2 = 106 c1 = 106 mod 11 = 7 c = (11-c1) mod 10 = 4 mod 10 = 4 Other variants of these check digit algorithms exist and may be used by local bilateral site agreement. Note: The check digit and code identifying check digit scheme are null if ID is alphanumeric. The assigning authority is a unique name of the system (or organization or agency or department) that creates the data. . Refer to User-defined Table 0363 – Assigning authority for suggested values. The reader is referred to the CX.9 and the CX.10 if there is a need to transmit values with semantic meaning for an assigning jurisdiction or assigning department or agency in addition to, or instead of, an assigning authority. However, all 3 components may be valued. If, in so doing, it is discovered that the values in CX.9 and/or CX.10 conflict with CX.4, the user would look to the Message Profile or other implementation agreement for a statement as to which takes precedence. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the patient. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component), may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The first date, if known, on which the identifier is valid and active. The last date, if known, on which the identifier is valid and active. The geo-political body that assigned the identifier in component 1. Refer to HL7 Table 0399 Country Code in section 2.15.9.17 for valid values if the administrative unit under whose jurisdiction the identifier was issued is a country. Refer to User-Defined Table 0347 State/Province for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a state or province. This table is country specific. In the US postal codes may be used. Refer to User-defined Table –0289 County/Parish for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a county or parish. The reader is referred to the CX.4, if there is a need to transmit this information as an OID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. Refer to User-defined Table –0530 Organizations, Agency, Department for suggested values if the administrative unit under whose jurisdiction the identifier was issued is an organization, agency or department. This is populated with site-specific assigning authorities. It also should contain national or international codes when CX-5 Identifier Type may be assigned by more than one authority within a governmental or organizational unit. For example, a federal government may have 2 departments that assign a military identifier, its Veterans Affairs department and its department of defense. It is not recommended to include values for entities such as Social Security Administration (SSA), Immigration and Naturalization Service (INS), Center for Medicare and Medicaid Services (CMS) because they are included in the identifier type table. In these cases the name of the country plus the identifier type yields the correct interpretation of the identifier in component one. Likewise, entries like department of motor vehicles (DMV) and licensing boards are not recommended for inclusion because the combination of state and identifier type yields the correct interpretation of the identifier in component one. This approach is not to be confused with the detailed information provided in the chapter 15 segments that have provision for specifying the precise granting body and issuing body information needed in personnel management messages. Example 1: <Identifier> plus <Visa> yields a unique identifier. Example 2: <Identifier> plus <state> plus <DLN> yields a unique driver’s license number. Example 3: <Identifier> plus <country> plus <INS> yields a unique immigration number. The reader is referred to the CX.4, if there is a need to transmit this information as an OID. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Guarantor Name This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, "FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. This component cannot be fully expressed. Identified as v 2.4 erratum. Retained for backward compatibility only as of v 2.5. Refer to Effective Date and Expiration Date components. This component contains the start and end date/times, which define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 0444 – Name assembly order for valid values. The first date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. Guarantor Spouse Name This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, "FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. This component cannot be fully expressed. Identified as v 2.4 erratum. Retained for backward compatibility only as of v 2.5. Refer to Effective Date and Expiration Date components. This component contains the start and end date/times, which define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 0444 – Name assembly order for valid values. The first date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. Guarantor Address See section 2.A.67, "SAD – street address" for description of components. This component specifies the street or mailing address of a person or institution. When referencing an institution, this first component is used to specify the institution name. When used in connection with a person, this component specifies the first line of the address. Street Name Dwelling Number Second line of address. In US usage, it qualifies address. Examples: Suite 555 or Fourth Floor. When referencing an institution, this component specifies the street address. This component specifies the city, or district or place where the addressee is located depending upon the national convention for formatting addresses for postal usage. This component specifies the state or province where the addressee is located. State or province should be represented by the official postal service codes for that country. This component specifies the zip or postal code where the addressee is located. Zip or postal codes should be represented by the official codes for that country. In the US, the zip code takes the form 99999[-9999], while the Canadian postal code takes the form A9A9A9, and the Australian Postcode takes the form 9999. This component specifies the country where the addressee is locatedHL7 specifies that the 3-character (alphabetic) form of ISO 3166 be used for the country code. Refer to HL7 Table 0399 – Country code in section 2.15.9.17 for valid values. This component specifies the kind or type of address. Refer to HL7 Table 0190 - Address type for valid values. This component specifies any other geographic designation. It includes county, bioregion, SMSA, etc. A code that represents the county in which the specified address resides. User-defined Table 0289 - County/parish is used as the HL7 identifier for the user-defined table of values for this component. When this component is used to represent the county (or parish), component 8 <other geographic designation> should not duplicate it (i.e., the use of <other geographic designation> to represent the county is allowed only for the purpose of backward compatibility, and should be discouraged in this and future versions of HL7). Allowable values: codes defined by government. A code that represents the census tract in which the specified address resides. User-defined Table 0288 - Census tract is used as the HL7 identifier for the user-defined table of values for this component. Allowable Values: codes defined by government. Different <name/address types> and representations of the same name/address should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: Also note that this new component remains in "alphabetic" representation with each repetition of the fields using these data types. I.e. even though the address may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component cannot be fully expressed. Identified as v 2.4 erratum. Retained for backward compatibility only as of v 2.5. Refer to Effective Date and Expiration Date components. This component contains the start and end date/times, which define the period in which this address was valid. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Guarantor Ph Num - Home Specifies the telephone number in a predetermined format that includes an optional extension, beeper number and comment. This component has been retained for backward compatibility only as of version 2.3. Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C any text] Note: Because this component has been deprecated a new data type has not been defined to replace the formatted ST. A code that represents a specific use of a telecommunication number. Refer to HL7 Table 0201 - Telecommunication use code for valid values. A code that represents the type of telecommunication equipment. Refer to HL7 Table 0202 - Telecommunication equipment type for valid values. Internationalization note: To make this data type interoperate with CEN’s Telecommunication data attribute group, we allow use of the second component for email addresses. The presence of an email address is specified by the addition of the value NET to the Phone Use Code table, and the type of Internet address is specified with the values Internet and X.400 to the Phone Equipment Type table. When used for an Internet address, the first component of the XTN data type will be null. If the @-sign is being used as a subcomponent delimiter, the HL7 subcomponent escape sequence may be used when encoding an Internet address (see Section Country Code (NM). Country Code Area/City Code Local Number Extension Contains comments with respect to the telephone number. The characters established within a company’s internal telephone system network used as a prefix to the Extension component for internal dialing. Note that the use of Extension Prefix requires that the Extension component be valued and that digits, as well as special characters (e.g., *, #) may be used. The characters established within a company’s internal telephone system used in place of the (external) telephone number to facilitate calling because its length is shorter than that of the telephone number. Note that digits, as well as special characters (e.g., *, #) may be used. An expression of the telephone number as an unparsible string. The phone number was entered as free text and sending system does not know how to parse it. Guarantor Ph Num - Business Specifies the telephone number in a predetermined format that includes an optional extension, beeper number and comment. This component has been retained for backward compatibility only as of version 2.3. Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C any text] Note: Because this component has been deprecated a new data type has not been defined to replace the formatted ST. A code that represents a specific use of a telecommunication number. Refer to HL7 Table 0201 - Telecommunication use code for valid values. A code that represents the type of telecommunication equipment. Refer to HL7 Table 0202 - Telecommunication equipment type for valid values. Internationalization note: To make this data type interoperate with CEN’s Telecommunication data attribute group, we allow use of the second component for email addresses. The presence of an email address is specified by the addition of the value NET to the Phone Use Code table, and the type of Internet address is specified with the values Internet and X.400 to the Phone Equipment Type table. When used for an Internet address, the first component of the XTN data type will be null. If the @-sign is being used as a subcomponent delimiter, the HL7 subcomponent escape sequence may be used when encoding an Internet address (see Section Country Code (NM). Country Code Area/City Code Local Number Extension Contains comments with respect to the telephone number. The characters established within a company’s internal telephone system network used as a prefix to the Extension component for internal dialing. Note that the use of Extension Prefix requires that the Extension component be valued and that digits, as well as special characters (e.g., *, #) may be used. The characters established within a company’s internal telephone system used in place of the (external) telephone number to facilitate calling because its length is shorter than that of the telephone number. Note that digits, as well as special characters (e.g., *, #) may be used. An expression of the telephone number as an unparsible string. The phone number was entered as free text and sending system does not know how to parse it. Guarantor Date/Time Of Birth The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Guarantor Administrative Sex Guarantor Type Guarantor Relationship Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Guarantor SSN Guarantor Date - Begin Guarantor Date - End Guarantor Priority Guarantor Employer Name This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, "FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. This component cannot be fully expressed. Identified as v 2.4 erratum. Retained for backward compatibility only as of v 2.5. Refer to Effective Date and Expiration Date components. This component contains the start and end date/times, which define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 0444 – Name assembly order for valid values. The first date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. Guarantor Employer Address See section 2.A.67, "SAD – street address" for description of components. This component specifies the street or mailing address of a person or institution. When referencing an institution, this first component is used to specify the institution name. When used in connection with a person, this component specifies the first line of the address. Street Name Dwelling Number Second line of address. In US usage, it qualifies address. Examples: Suite 555 or Fourth Floor. When referencing an institution, this component specifies the street address. This component specifies the city, or district or place where the addressee is located depending upon the national convention for formatting addresses for postal usage. This component specifies the state or province where the addressee is located. State or province should be represented by the official postal service codes for that country. This component specifies the zip or postal code where the addressee is located. Zip or postal codes should be represented by the official codes for that country. In the US, the zip code takes the form 99999[-9999], while the Canadian postal code takes the form A9A9A9, and the Australian Postcode takes the form 9999. This component specifies the country where the addressee is locatedHL7 specifies that the 3-character (alphabetic) form of ISO 3166 be used for the country code. Refer to HL7 Table 0399 – Country code in section 2.15.9.17 for valid values. This component specifies the kind or type of address. Refer to HL7 Table 0190 - Address type for valid values. This component specifies any other geographic designation. It includes county, bioregion, SMSA, etc. A code that represents the county in which the specified address resides. User-defined Table 0289 - County/parish is used as the HL7 identifier for the user-defined table of values for this component. When this component is used to represent the county (or parish), component 8 <other geographic designation> should not duplicate it (i.e., the use of <other geographic designation> to represent the county is allowed only for the purpose of backward compatibility, and should be discouraged in this and future versions of HL7). Allowable values: codes defined by government. A code that represents the census tract in which the specified address resides. User-defined Table 0288 - Census tract is used as the HL7 identifier for the user-defined table of values for this component. Allowable Values: codes defined by government. Different <name/address types> and representations of the same name/address should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: Also note that this new component remains in "alphabetic" representation with each repetition of the fields using these data types. I.e. even though the address may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component cannot be fully expressed. Identified as v 2.4 erratum. Retained for backward compatibility only as of v 2.5. Refer to Effective Date and Expiration Date components. This component contains the start and end date/times, which define the period in which this address was valid. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Guarantor Employer Phone Number Specifies the telephone number in a predetermined format that includes an optional extension, beeper number and comment. This component has been retained for backward compatibility only as of version 2.3. Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C any text] Note: Because this component has been deprecated a new data type has not been defined to replace the formatted ST. A code that represents a specific use of a telecommunication number. Refer to HL7 Table 0201 - Telecommunication use code for valid values. A code that represents the type of telecommunication equipment. Refer to HL7 Table 0202 - Telecommunication equipment type for valid values. Internationalization note: To make this data type interoperate with CEN’s Telecommunication data attribute group, we allow use of the second component for email addresses. The presence of an email address is specified by the addition of the value NET to the Phone Use Code table, and the type of Internet address is specified with the values Internet and X.400 to the Phone Equipment Type table. When used for an Internet address, the first component of the XTN data type will be null. If the @-sign is being used as a subcomponent delimiter, the HL7 subcomponent escape sequence may be used when encoding an Internet address (see Section Country Code (NM). Country Code Area/City Code Local Number Extension Contains comments with respect to the telephone number. The characters established within a company’s internal telephone system network used as a prefix to the Extension component for internal dialing. Note that the use of Extension Prefix requires that the Extension component be valued and that digits, as well as special characters (e.g., *, #) may be used. The characters established within a company’s internal telephone system used in place of the (external) telephone number to facilitate calling because its length is shorter than that of the telephone number. Note that digits, as well as special characters (e.g., *, #) may be used. An expression of the telephone number as an unparsible string. The phone number was entered as free text and sending system does not know how to parse it. Guarantor Employee ID Number The value of the identifier itself. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. The algorithm for calculating a Mod10 check digit is as follows: Assume you have an identifier - 12345. Take the odd digit positions, counting from the right, i.e., 531, multiply this number by 2 to get 1062. Take the even digit positions, starting from the right (i.e., 42), prepend these to the 1062 to get 421062. Add all of these six digits together to get 15. Subtract this number from the next highest multiple of 10, i.e., 20 - 15 to get 5. The Mod10 check digit is 5. The Mod10 check digit for 401 is 0; for 9999, it’s 4; for 99999999, it’s 8. The algorithm for calculating a Mod11 check digit is as follows: Terms d = digit of number starting from units digit, followed by 10’s position, followed by 100’s position, etc. w = weight of digit position starting with the units position, followed by 10’s position, followed by 100’s position etc. Values for w = 2, 3, 4, 5, 6, 7, 2, 3, 4, 5, 6, 7, etc. (repeats for each group of 6 digits) c = check digit Calculation (Step 1) m = sum of (d * w) for positions 1, 2, etc. starting with units digit for d = digit value starting with units position to highest order for w = weight value from 2 to 7 for every six positions starting with units digit (Step 2) c1 = m mod 11 (Step 3) if c1 = 0 then reset c1 = 1 (Step 4) = (11 - c1) mod 10 Example: If the number is 1234567, then the mod 11 check digit = 4 The calculations are: M = (7*2)+(6*3)+(5*4)+(4*5)+(3*6)+(2*7)+(1*2) = 14 + 18 + 20 + 20 + 18 + 14 + 2 = 106 c1 = 106 mod 11 = 7 c = (11-c1) mod 10 = 4 mod 10 = 4 Other variants of these check digit algorithms exist and may be used by local bilateral site agreement. Note: The check digit and code identifying check digit scheme are null if ID is alphanumeric. The assigning authority is a unique name of the system (or organization or agency or department) that creates the data. . Refer to User-defined Table 0363 – Assigning authority for suggested values. The reader is referred to the CX.9 and the CX.10 if there is a need to transmit values with semantic meaning for an assigning jurisdiction or assigning department or agency in addition to, or instead of, an assigning authority. However, all 3 components may be valued. If, in so doing, it is discovered that the values in CX.9 and/or CX.10 conflict with CX.4, the user would look to the Message Profile or other implementation agreement for a statement as to which takes precedence. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the patient. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component), may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The first date, if known, on which the identifier is valid and active. The last date, if known, on which the identifier is valid and active. The geo-political body that assigned the identifier in component 1. Refer to HL7 Table 0399 Country Code in section 2.15.9.17 for valid values if the administrative unit under whose jurisdiction the identifier was issued is a country. Refer to User-Defined Table 0347 State/Province for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a state or province. This table is country specific. In the US postal codes may be used. Refer to User-defined Table –0289 County/Parish for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a county or parish. The reader is referred to the CX.4, if there is a need to transmit this information as an OID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. Refer to User-defined Table –0530 Organizations, Agency, Department for suggested values if the administrative unit under whose jurisdiction the identifier was issued is an organization, agency or department. This is populated with site-specific assigning authorities. It also should contain national or international codes when CX-5 Identifier Type may be assigned by more than one authority within a governmental or organizational unit. For example, a federal government may have 2 departments that assign a military identifier, its Veterans Affairs department and its department of defense. It is not recommended to include values for entities such as Social Security Administration (SSA), Immigration and Naturalization Service (INS), Center for Medicare and Medicaid Services (CMS) because they are included in the identifier type table. In these cases the name of the country plus the identifier type yields the correct interpretation of the identifier in component one. Likewise, entries like department of motor vehicles (DMV) and licensing boards are not recommended for inclusion because the combination of state and identifier type yields the correct interpretation of the identifier in component one. This approach is not to be confused with the detailed information provided in the chapter 15 segments that have provision for specifying the precise granting body and issuing body information needed in personnel management messages. Example 1: <Identifier> plus <Visa> yields a unique identifier. Example 2: <Identifier> plus <state> plus <DLN> yields a unique driver’s license number. Example 3: <Identifier> plus <country> plus <INS> yields a unique immigration number. The reader is referred to the CX.4, if there is a need to transmit this information as an OID. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Guarantor Employment Status Guarantor Organization Name The name of the specified organization. A code that represents the type of name i.e., legal name, display name. Refer to User-defined Table 0204 - Organizational Name Type for suggested values. This component has been retained for backward compatibility only as of v 2.5. It is recommended to use component 10 Organization identifier that accommodates alphanumeric identifiers. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. The check digit scheme codes are defined in HL7 Table 0061 - Check digit scheme. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Assigning authorities are unique across a given HL7 implementation. Refer to User-defined Table 0363 - Assigning Authority for suggested values. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e. even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation code for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component contains the sequence of characters (the code) that uniquely identifies the item being referenced by XON.1 Organization Name. This component replaces XON.3 ID Number as of v 2.5. Note: The check digit and code identifying check digit scheme are null if Organization identifier is alphanumeric. Guarantor Billing Hold Flag Guarantor Credit Rating Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Guarantor Death Date And Time The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Guarantor Death Flag Guarantor Charge Adjustment Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Guarantor Household Annual Income The only required component; usually containing a decimal point. Note that each component of the MO data type (Section 2.A.41, "MO - money") is a subcomponent here. The first component is a quantity. The second component is the denomination in which the quantity is expressed. The values for the denomination component are those specified in ISO-4217. If the denomination is not specified, MSH-17-country code is used to determine the default. Example: |99.50^USD| where USD is the ISO 4217 code for the U.S. American dollar. A coded value, data type ID. Refer to HL7 Table 0205 - Price type for valid values. Each is a NM data type; together they specify the "range". The range can be defined as either time or quantity. For example, the range can indicate that the first 10 minutes of the procedure has one price. Another repetition of the data type can use the range to specify that the following 10 to 60 minutes of the procedure is charged at another price per; a final repetition can specify that the final 60 to N minutes of the procedure at a third price. Note that, if the <price type> component is TP, both <from value> and <to value> may be null. See <from value> above. A coded value, data type CE, defined by the standard table of units for either time or quantity (see for example, the tables in Section 7.1.4, "Coding schemes"). This describes the units associated with the range, e.g., seconds, minutes, hours, days, quantity (i.e., count); it is required if <from value> and <to value> are present. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Refer to HL7 Table 0298 - CP range type for valid values. Guarantor Household Size Guarantor Employer ID Number The value of the identifier itself. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. The algorithm for calculating a Mod10 check digit is as follows: Assume you have an identifier - 12345. Take the odd digit positions, counting from the right, i.e., 531, multiply this number by 2 to get 1062. Take the even digit positions, starting from the right (i.e., 42), prepend these to the 1062 to get 421062. Add all of these six digits together to get 15. Subtract this number from the next highest multiple of 10, i.e., 20 - 15 to get 5. The Mod10 check digit is 5. The Mod10 check digit for 401 is 0; for 9999, it’s 4; for 99999999, it’s 8. The algorithm for calculating a Mod11 check digit is as follows: Terms d = digit of number starting from units digit, followed by 10’s position, followed by 100’s position, etc. w = weight of digit position starting with the units position, followed by 10’s position, followed by 100’s position etc. Values for w = 2, 3, 4, 5, 6, 7, 2, 3, 4, 5, 6, 7, etc. (repeats for each group of 6 digits) c = check digit Calculation (Step 1) m = sum of (d * w) for positions 1, 2, etc. starting with units digit for d = digit value starting with units position to highest order for w = weight value from 2 to 7 for every six positions starting with units digit (Step 2) c1 = m mod 11 (Step 3) if c1 = 0 then reset c1 = 1 (Step 4) = (11 - c1) mod 10 Example: If the number is 1234567, then the mod 11 check digit = 4 The calculations are: M = (7*2)+(6*3)+(5*4)+(4*5)+(3*6)+(2*7)+(1*2) = 14 + 18 + 20 + 20 + 18 + 14 + 2 = 106 c1 = 106 mod 11 = 7 c = (11-c1) mod 10 = 4 mod 10 = 4 Other variants of these check digit algorithms exist and may be used by local bilateral site agreement. Note: The check digit and code identifying check digit scheme are null if ID is alphanumeric. The assigning authority is a unique name of the system (or organization or agency or department) that creates the data. . Refer to User-defined Table 0363 – Assigning authority for suggested values. The reader is referred to the CX.9 and the CX.10 if there is a need to transmit values with semantic meaning for an assigning jurisdiction or assigning department or agency in addition to, or instead of, an assigning authority. However, all 3 components may be valued. If, in so doing, it is discovered that the values in CX.9 and/or CX.10 conflict with CX.4, the user would look to the Message Profile or other implementation agreement for a statement as to which takes precedence. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the patient. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component), may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The first date, if known, on which the identifier is valid and active. The last date, if known, on which the identifier is valid and active. The geo-political body that assigned the identifier in component 1. Refer to HL7 Table 0399 Country Code in section 2.15.9.17 for valid values if the administrative unit under whose jurisdiction the identifier was issued is a country. Refer to User-Defined Table 0347 State/Province for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a state or province. This table is country specific. In the US postal codes may be used. Refer to User-defined Table –0289 County/Parish for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a county or parish. The reader is referred to the CX.4, if there is a need to transmit this information as an OID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. Refer to User-defined Table –0530 Organizations, Agency, Department for suggested values if the administrative unit under whose jurisdiction the identifier was issued is an organization, agency or department. This is populated with site-specific assigning authorities. It also should contain national or international codes when CX-5 Identifier Type may be assigned by more than one authority within a governmental or organizational unit. For example, a federal government may have 2 departments that assign a military identifier, its Veterans Affairs department and its department of defense. It is not recommended to include values for entities such as Social Security Administration (SSA), Immigration and Naturalization Service (INS), Center for Medicare and Medicaid Services (CMS) because they are included in the identifier type table. In these cases the name of the country plus the identifier type yields the correct interpretation of the identifier in component one. Likewise, entries like department of motor vehicles (DMV) and licensing boards are not recommended for inclusion because the combination of state and identifier type yields the correct interpretation of the identifier in component one. This approach is not to be confused with the detailed information provided in the chapter 15 segments that have provision for specifying the precise granting body and issuing body information needed in personnel management messages. Example 1: <Identifier> plus <Visa> yields a unique identifier. Example 2: <Identifier> plus <state> plus <DLN> yields a unique driver’s license number. Example 3: <Identifier> plus <country> plus <INS> yields a unique immigration number. The reader is referred to the CX.4, if there is a need to transmit this information as an OID. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Guarantor Marital Status Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Guarantor Hire Effective Date Employment Stop Date Living Dependency Ambulatory Status Citizenship Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Primary Language Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Living Arrangement Publicity Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Protection Indicator Student Indicator Religion Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Mother's Maiden Name This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, "FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. This component cannot be fully expressed. Identified as v 2.4 erratum. Retained for backward compatibility only as of v 2.5. Refer to Effective Date and Expiration Date components. This component contains the start and end date/times, which define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 0444 – Name assembly order for valid values. The first date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. Nationality Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Ethnic Group Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Contact Person's Name This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, "FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. This component cannot be fully expressed. Identified as v 2.4 erratum. Retained for backward compatibility only as of v 2.5. Refer to Effective Date and Expiration Date components. This component contains the start and end date/times, which define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 0444 – Name assembly order for valid values. The first date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. Contact Person's Telephone Number Specifies the telephone number in a predetermined format that includes an optional extension, beeper number and comment. This component has been retained for backward compatibility only as of version 2.3. Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C any text] Note: Because this component has been deprecated a new data type has not been defined to replace the formatted ST. A code that represents a specific use of a telecommunication number. Refer to HL7 Table 0201 - Telecommunication use code for valid values. A code that represents the type of telecommunication equipment. Refer to HL7 Table 0202 - Telecommunication equipment type for valid values. Internationalization note: To make this data type interoperate with CEN’s Telecommunication data attribute group, we allow use of the second component for email addresses. The presence of an email address is specified by the addition of the value NET to the Phone Use Code table, and the type of Internet address is specified with the values Internet and X.400 to the Phone Equipment Type table. When used for an Internet address, the first component of the XTN data type will be null. If the @-sign is being used as a subcomponent delimiter, the HL7 subcomponent escape sequence may be used when encoding an Internet address (see Section Country Code (NM). Country Code Area/City Code Local Number Extension Contains comments with respect to the telephone number. The characters established within a company’s internal telephone system network used as a prefix to the Extension component for internal dialing. Note that the use of Extension Prefix requires that the Extension component be valued and that digits, as well as special characters (e.g., *, #) may be used. The characters established within a company’s internal telephone system used in place of the (external) telephone number to facilitate calling because its length is shorter than that of the telephone number. Note that digits, as well as special characters (e.g., *, #) may be used. An expression of the telephone number as an unparsible string. The phone number was entered as free text and sending system does not know how to parse it. Contact Reason Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Contact Relationship Job Title Job Code/Class This component contains the person’s job code. User-defined Table 0327 - Job code is used as the HL7 identifier for the user-defined table of values for this component. This component contains the person’s employee classification. Refer to User-defined Table 0328 - Employee classification for suggested values. This component contains the text of the job description. This will accommodate systems where job descriptions are not codified. Guarantor Employer's Organization Name The name of the specified organization. A code that represents the type of name i.e., legal name, display name. Refer to User-defined Table 0204 - Organizational Name Type for suggested values. This component has been retained for backward compatibility only as of v 2.5. It is recommended to use component 10 Organization identifier that accommodates alphanumeric identifiers. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. The check digit scheme codes are defined in HL7 Table 0061 - Check digit scheme. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Assigning authorities are unique across a given HL7 implementation. Refer to User-defined Table 0363 - Assigning Authority for suggested values. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e. even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation code for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component contains the sequence of characters (the code) that uniquely identifies the item being referenced by XON.1 Organization Name. This component replaces XON.3 ID Number as of v 2.5. Note: The check digit and code identifying check digit scheme are null if Organization identifier is alphanumeric. Handicap Job Status Guarantor Financial Class This component contains the financial class assigned to a person. User-defined Table 0064 - Financial class is used as the HL7 identifier for the user-defined table of values for this component. This component contains the effective date/time of the person’s assignment to the financial class specified in the first component. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Guarantor Race Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Guarantor Birth Place VIP Indicator Relevante allergieën, antibioticaovergevoeligheden Set ID. Dit veld bevat het nummer dat dit segment identificeert binnen het bericht. Bij de eerste keer dat het segment voorkomt, moet het volgnummer 1 zijn, bij de tweede keer is het 2, enzovoorts. Allergen Type Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Allergen Code/Mnemonic/Description Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Allergy Severity Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. - Order Control. Bepaalt de functie van het aanvraagsegment. Zie HL7 Tabel 0119 - Order Control Codes And Their Meaning voor geldige waarden. De initiële status van een aanvraag is altijd "NW". Het ORC-segment kan voorkomen in diverse berichten, waaronder het aanvraagbericht OM^O21 en het aanvraagbevestigingbericht ORL^O22 en uiteindelijk ook het resultaatbericht OUL^R22. Of er gebruik wordt gemaakt van ORL^O22, hangt af van lokale afspraken. Order Control Codes / Trigger Event MatrixCodeOML^O21ORL^O22OUL^R22toelichtingNWYNieuwOKYYOK, order geaccepteerdUAYOrder niet geaccepteerd (unable to accept) De aanvrager kan aanvragen eventueel nog aanvullen, annuleren en stoppen: HL7 Tabel 0119 heeft voor alle gevallen aparte codes. Er wordt binnen Lab2Lab in principe geen gebruik wordt gemaakt van meer complexe processturing dan hierboven afgebeeld, maar hier kunnen lokaal andere afspraken over worden gemaakt.Aanvragen voor RIVM Type-Ned moeten de code NW bevatten en hierop volgt een aanvraagbevestiging met OK of UA per aanvraag. Aanvraagnummer (Placer Order Number) van het uitbestedende laboratorium. Om unieke identificatie te kunnen garanderen, is de verwachting dat deze identificatie begint met het driecijferige labid van het lab dat dit nummer heeft uitgedeeld. The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Aanvraagnummer (Filler Order Number) van het inbestedende laboratorium. Om unieke identificatie te kunnen garanderen, is de verwachting dat deze identificatie begint met het driecijferige labid van het lab dat dit nummer heeft uitgedeeld. Het Aanvraagnummer van het inbestedende laboratorium wordt verwacht bij ieder ORC segment waarvoor een inbestedend laboratorium resultaten produceert The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Aanvraagnummer (Placer Group Number) van het uitbestedende laboratorium. Als uit een aanvraag, een of meerdere andere aanvragen worden gegenereerd, bijvoorbeeld separate isolaatgevoeligheidpanels, dan bevat dit veld de koppeling naar de aanvraag waaruit ORC|2 is voortgekomen. Om unieke identificatie te kunnen garanderen, is de verwachting dat deze identificatie begint met het driecijferige labid van het lab dat dit nummer heeft uitgedeeld. The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Order Status Response Flag Quantity/Timing This component specifies the quantity of the service that should be provided at each service interval. For example, if two blood cultures are to be obtained every 4 hours, the quantity would be 2. If three units of blood are to be typed and cross-matched, the quantity would be 3. The default value is 1. When units are required, they can be added, specified by a subcomponent delimiter. Note: The component contains the complex data type CQ and cannot be fully expressed. CQ cannot be legally expressed when embedded within another data type. This component specifies the numeric quantity or amount of an entity. This component species the units in which the quantity is expressed. Field-by-field, default units may be defined within the specifications. When the quantity is measured in the default units, the units need not be transmitted. If the quantity is recorded in units different from the default, the units must be transmitted. Determines the interval between repeated services. The default is one time only. The repeating frequency with which the treatment is to be administered. It is similar to the frequency and SIG code tables used in order entry systems. Refer to User-defined Table 0335 - Repeat pattern for suggested values. The first component may repeat, with repeat values separated by a space. The repeats are interpreted as connected by logical ANDs. Example: Twice per day, every other day: BID QOD Three times per day, Monday Wednesday and Friday: TID QJ135 Because of this syntax, repeat values should never contain blanks. This component explicitly lists the actual times referenced by the code in the first component, in the following format: HHMM,HHMM,HHMM,.… This second component will be used to clarify the first component in cases where the actual times vary within an institution. If the time of the order spans more than a single day, this new component is only practical if the same times of administration occur for each day of the order. If the actual start time of the order (as given by the fourth component of the quantity/timing field) is after the first explicit time, the first administration is taken to be the first explicit time after the start time. In the case where the patient moves to a location having a different set of explicit times, the existing order may be updated with a new quantity/timing field showing the changed explicit times. This component indicates how long the service should continue after it is started. The default is INDEF (do indefinitely). This component is coded as follows: Value Description Comments S<integer> <integer> seconds M<integer> <integer> minutes H<integer> <integer> hours D<integer> <integer> days W<integer> <integer> weeks L<integer> <integer> months X<integer> <integer> times at interval specified in the order. A request for 2 blood cultures Q2H X3 would imply obtaining 2 blood cultures 3 different times at 2-hour intervals for a total of 6 blood cultures. T<integer> at the interval and amount stated until a total of <integer> "DOSAGE" is accumulated. Units would be assumed to be the same as in the QUANTITY field. INDEF do indefinitely - also the default This component may be specified by the orderer, in which case it indicates the earliest date/time at which the services should be started. In many cases, however, the start date/time will be implied or will be defined by other fields in the order record (e.g., urgency ‑ STAT). In such a case, this field will be empty. The filling service will often record a value in this field after receipt of the order, however, and compute an end time on the basis of the start date/time for the filling service’s internal use. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| When filled in by the requester of the service, this component should contain the latest date/time that the service should be performed. If it has not been performed by the specified time, it should not be performed at all. The requester may not always fill in this value, yet the filling service may fill it in on the basis of the instruction it receives and the actual start time. Regardless of the value of the end date/time, the service should be stopped at the earliest of the date/times specified by either the duration or the end date/time. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| This component describes the urgency of the request. The following values are suggested (the default for Priority is R): Value Description Comments S Stat With highest priority A ASAP Fill after S orders R Routine Default P Preop C Callback T Timing critical A request implying that it is critical to come as close as possible to the requested time, e.g., for a trough antimicrobial level. PRN As needed If using the value "T" (timing critical), the degree of criticality can be specified thus: Format: Value Description Comments TS<integer> timing critical within <integer> seconds TM<integer> timing critical within <integer> minutes TH<integer> timing critical within <integer> hours TD<integer> timing critical within <integer> days TW<integer> timing critical within <integer> weeks TL<integer> timing critical within <integer> months For the sequential orders specification, these values specify the time criticality with which the predecessor order must be followed by the given order. The priority component may repeat; separate repeating values with a space. This is a free text component that describes the conditions under which the drug is to be given. For example, PRN pain, or to keep blood pressure below 110. The presence of text in this field should be taken to mean that human review is needed to determine the how and/or when this drug should be given. This component is a full text version of the instruction (optional). This non‑null component indicates that a second timing specification is to follow using the repeat delimiter. Refer to HL7 table 0472 - TQ Conjunction ID for valid values Usage Note: There are many situations, such as the creation of an order for a group of intravenous (IV) solutions, where the sequence of the individual intravenous solutions (each a service in itself) needs to be specified, e.g., hyperalimentation with multi-vitamins in every third bottle. There are other situations where part of the order’s instructions contains a results condition of some type, such as "PRN pain". There is currently a free text "condition" component of ORC-7-quantity/timing, which allows any condition to be specified. However, to support a fully encoded version of order sequencing, or results condition, we have defined in the following paragraphs a 10th component of ORC-7-quantity/timing. The sequencing conditions supported by this 10th component are based on the completion of a predecessor service. Identifies whether sequence conditions or a repeating cycle of orders is defined. Refer to HL7-defined Table 0524 – Sequence condition for valid values. Contains the first component of the placer order number, entity identifier. Contains the second component of the placer order number, namespace ID. Refer to user-defined table 0363 - Assigning Authority for suggested values. Contains the first component of the filler order number, entity identifier. Contains the second component of the filler order number, namespace ID. Refer to user-defined table 0363 - Assigning Authority for suggested values Defines the relationship between the start/end of the related predecessor or successor order and the current order from ORC-2, 3 or 4. The acceptable condition values have the form commonly used in project planning methodologies in the following format: <one of "SS", "EE", "SE", or "ES"> +/- <time>. The first letter stands for start (S) or end (E) of predecessor order, where the predecessor is defined by the placer or filler order number in subcomponents 1,2 or subcomponents 3,4. The second letter stands for the start (S) or end (E) of the successor order, where the successor order is the order containing this quantity/timing specification. The time specifies the interval between the predecessor and successor starts or ends (see following examples). Where <time> is defined as: Example Description Comment S<integer> do for <integer> seconds M<integer> do for <integer> minutes H<integer> do for <integer> hours D<integer> do for <integer> days W<integer> do for <integer> weeks L<integer> do for <integer> months The maximum number of repeats to be used only on cyclic groups. The total number of repeats is constrained by the end date/time of the last repeat or the end date/time of the parent, whichever is first. Contains the next to the last component of the placer order number, universal ID. Contains the last component of the placer order number. Refer to HL7 table 0301 - Universal ID Type for valid values. Contains the next to the last component of the filler order number, universal ID. Contains the last component of the placer order number. Refer to HL7 table 0301 - Universal ID Type for valid values. This component contains the duration for a single performance of a service, e.g., whirlpool twenty minutes three times per day for three days. It is optional within TQ and does not repeat. Note: The component delimiter in this CQ is demoted to a subcomponent delimiter. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. This component contains the total number of occurrences of a service that should result from this order. It is optional within TQ and does not repeat. If both the end date/time and the total occurrences are valued and the occurrences would extend beyond the end date/time, then the end date/time takes precedence. Otherwise the number of occurrences takes precedence. Dit veld relateert een child aan zijn parent wanneer een parent-child relatie van toepassing is. ORC-8-parent is hetzelfde als OBR-29-parent. Als de parent niet bestaat in ORC, dan moet deze aanwezig zijn in de bijbehorende OBR. Specifies an identifier assigned to an entity by the placer system. For example, the component might be used to convey the following: placer order number of the parent order the specimen identifier as assigned by the placer. A location identifier assigned (or used by) the placer. The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Specifies an identifier assigned to an entity by the filler system. For example, the component might convey the following: filler order number of the parent order the specimen identifier as assigned by the filler. A location identifier assigned (or used by) the filler. The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Date/Time of Transaction The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Entered By This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Verified By This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Ordering Provider This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Enterer's Location This component specifies the code for the point where patient care is administered. It is conditional on PL.6 Person Location Type (e.g., nursing unit or department or clinic). After floor, it is the most general patient location designation. Refer to User-defined Table 0302 - Point of care for suggested values. This component specifies the code for the patient's room. After point of care, it is the most general person location designation. Refer to User-defined Table 0303 - Room for suggested values. This component specifies the code for the patient's bed. After room, it is the most general person location designation. Refer to User-defined Table 0304 - Bed for suggested values. This component is subject to site interpretation but generally describes the highest level physical designation of an institution, medical center or enterprise. It is the most general person location designation. (See Section 2.A.33, "HD - hierarchic designator") for discussion of data type. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be redefined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. This component specifies the code for the status or availability of the location. For example, it may convey bed status. Refer to User-defined Table 0306 - Location status for suggested values. Person location type is the categorization of the person’s location defined by facility, building, floor, point of care, room or bed. Although not a required field, when used, it may be the only populated field. It usually includes values such as nursing unit, department, clinic, SNF, physician’s office. Refer to User-defined Table 0305 - Person location type for suggested values. Required if known This component specifies the code for the building where the person is located. After facility, it is the most general person location designation. Refer to User-defined Table 0307 - Building for suggested values. This component specifies the code for the floor where the person is located. After building, it is the most general person location designation. Refer to User-defined Table 0308 - Floor for suggested values. This component describes the location in free text. The unique identifier that represents the physical location as a whole without regard for the individual components. This accommodates sites that may have a different method of defining physical units or who may code at a less granular level. For example, point of care, room, and bed may be 1 indivisible code. The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The entity that creates the data for the individual physical location components. If populated, it should be the authority for all components populated. Refer to User-defined Table 0363 – Assigning authority for suggested values for the first sub-component of the HD component, <namespace ID>. This component makes it possible for codes to be differentiated when the field in which this data type is used repeats. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementors may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Call Back Phone Number Specifies the telephone number in a predetermined format that includes an optional extension, beeper number and comment. This component has been retained for backward compatibility only as of version 2.3. Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C any text] Note: Because this component has been deprecated a new data type has not been defined to replace the formatted ST. A code that represents a specific use of a telecommunication number. Refer to HL7 Table 0201 - Telecommunication use code for valid values. A code that represents the type of telecommunication equipment. Refer to HL7 Table 0202 - Telecommunication equipment type for valid values. Internationalization note: To make this data type interoperate with CEN’s Telecommunication data attribute group, we allow use of the second component for email addresses. The presence of an email address is specified by the addition of the value NET to the Phone Use Code table, and the type of Internet address is specified with the values Internet and X.400 to the Phone Equipment Type table. When used for an Internet address, the first component of the XTN data type will be null. If the @-sign is being used as a subcomponent delimiter, the HL7 subcomponent escape sequence may be used when encoding an Internet address (see Section Country Code (NM). Country Code Area/City Code Local Number Extension Contains comments with respect to the telephone number. The characters established within a company’s internal telephone system network used as a prefix to the Extension component for internal dialing. Note that the use of Extension Prefix requires that the Extension component be valued and that digits, as well as special characters (e.g., *, #) may be used. The characters established within a company’s internal telephone system used in place of the (external) telephone number to facilitate calling because its length is shorter than that of the telephone number. Note that digits, as well as special characters (e.g., *, #) may be used. An expression of the telephone number as an unparsible string. The phone number was entered as free text and sending system does not know how to parse it. Order Effective Date/Time The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Order Control Code Reason. Kan de reden bij de waarde in ORC|1 bevatten. Dit is vooral relevant bij waarden anders dan NW en OK. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Entering Organization Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Entering Device Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Action By This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Advanced Beneficiary Notice Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Ordering Facility Name The name of the specified organization. A code that represents the type of name i.e., legal name, display name. Refer to User-defined Table 0204 - Organizational Name Type for suggested values. This component has been retained for backward compatibility only as of v 2.5. It is recommended to use component 10 Organization identifier that accommodates alphanumeric identifiers. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. The check digit scheme codes are defined in HL7 Table 0061 - Check digit scheme. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Assigning authorities are unique across a given HL7 implementation. Refer to User-defined Table 0363 - Assigning Authority for suggested values. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e. even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation code for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component contains the sequence of characters (the code) that uniquely identifies the item being referenced by XON.1 Organization Name. This component replaces XON.3 ID Number as of v 2.5. Note: The check digit and code identifying check digit scheme are null if Organization identifier is alphanumeric. Ordering Facility Address Adres straat - Vanaf versie 2.4 is ‘street address’ een samengesteld datatype, waar in de verschillende onderdelen van het adres in verschillende subcomponenten kunnen worden opgenomen This component specifies the street or mailing address of a person or institution. When referencing an institution, this first component is used to specify the institution name. When used in connection with a person, this component specifies the first line of the address. Street Name Dwelling Number Huisnummertoevoeging Woonplaats Staat of provincie. Meestal niet relevant, maar gebruiken bij plaatsnamen in meerdere provincies zoals Afferden (Gelderland en Limburg) en Bergen (Noord-Holland en Limburg) Postcode, indien een Nederlandse postcode dan zonder spaties dus bijv. 2316XA. Merk op dat de HL7v3 specificatie met een spatie voorschrijft. Er is hier bewust gekozen voor compatibiliteit met de officiële HL7v2.4 NL specificatie. Land Adrestype. Voor het eerste adres moet deze de waarde ‘M’ (mailing) hebben. Andere adressen kunnen ook worden doorgegeven, zoals bijv. huisadres (‘H’), of tijdelijk/verblijfsadres (‘C’). Andere geografische aanduiding. N.v.t. voor Nederlandse adressen County/graafschap code. N.v.t. voor Nederlandse adressen Census tract. N.v.t. voor Nederlandse adressen. Representatiecode adres. N.v.t. voor Nederlandse adressen Adres geldigheidsperiode. Hierin kunnen eventueel de begin- en einddatum worden doorgegeven waarbinnen een adres geldig is. Dit kan bijv. voor tijdelijke adressen relevant zijn. Het is echter gemarkeerd als obsoleet en behouden voor backward compatbility in versie 2.5. Zie in plaats daarvan XAD.13 en XAD.14. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. Geldigheidsdatum. De eerste datum, indien bekend, waarop het adres geldig is/was en actief. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Verloopdatum. De laatste datum, indien bekend, waarop het adres geldig is/was en actief. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Ordering Facility Phone Number Specifies the telephone number in a predetermined format that includes an optional extension, beeper number and comment. This component has been retained for backward compatibility only as of version 2.3. Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C any text] Note: Because this component has been deprecated a new data type has not been defined to replace the formatted ST. A code that represents a specific use of a telecommunication number. Refer to HL7 Table 0201 - Telecommunication use code for valid values. A code that represents the type of telecommunication equipment. Refer to HL7 Table 0202 - Telecommunication equipment type for valid values. Internationalization note: To make this data type interoperate with CEN’s Telecommunication data attribute group, we allow use of the second component for email addresses. The presence of an email address is specified by the addition of the value NET to the Phone Use Code table, and the type of Internet address is specified with the values Internet and X.400 to the Phone Equipment Type table. When used for an Internet address, the first component of the XTN data type will be null. If the @-sign is being used as a subcomponent delimiter, the HL7 subcomponent escape sequence may be used when encoding an Internet address (see Section Country Code (NM). Country Code Area/City Code Local Number Extension Contains comments with respect to the telephone number. The characters established within a company’s internal telephone system network used as a prefix to the Extension component for internal dialing. Note that the use of Extension Prefix requires that the Extension component be valued and that digits, as well as special characters (e.g., *, #) may be used. The characters established within a company’s internal telephone system used in place of the (external) telephone number to facilitate calling because its length is shorter than that of the telephone number. Note that digits, as well as special characters (e.g., *, #) may be used. An expression of the telephone number as an unparsible string. The phone number was entered as free text and sending system does not know how to parse it. Ordering Provider Address Adres straat - Vanaf versie 2.4 is ‘street address’ een samengesteld datatype, waar in de verschillende onderdelen van het adres in verschillende subcomponenten kunnen worden opgenomen This component specifies the street or mailing address of a person or institution. When referencing an institution, this first component is used to specify the institution name. When used in connection with a person, this component specifies the first line of the address. Street Name Dwelling Number Huisnummertoevoeging Woonplaats Staat of provincie. Meestal niet relevant, maar gebruiken bij plaatsnamen in meerdere provincies zoals Afferden (Gelderland en Limburg) en Bergen (Noord-Holland en Limburg) Postcode, indien een Nederlandse postcode dan zonder spaties dus bijv. 2316XA. Merk op dat de HL7v3 specificatie met een spatie voorschrijft. Er is hier bewust gekozen voor compatibiliteit met de officiële HL7v2.4 NL specificatie. Land Adrestype. Voor het eerste adres moet deze de waarde ‘M’ (mailing) hebben. Andere adressen kunnen ook worden doorgegeven, zoals bijv. huisadres (‘H’), of tijdelijk/verblijfsadres (‘C’). Andere geografische aanduiding. N.v.t. voor Nederlandse adressen County/graafschap code. N.v.t. voor Nederlandse adressen Census tract. N.v.t. voor Nederlandse adressen. Representatiecode adres. N.v.t. voor Nederlandse adressen Adres geldigheidsperiode. Hierin kunnen eventueel de begin- en einddatum worden doorgegeven waarbinnen een adres geldig is. Dit kan bijv. voor tijdelijke adressen relevant zijn. Het is echter gemarkeerd als obsoleet en behouden voor backward compatbility in versie 2.5. Zie in plaats daarvan XAD.13 en XAD.14. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. Geldigheidsdatum. De eerste datum, indien bekend, waarop het adres geldig is/was en actief. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Verloopdatum. De laatste datum, indien bekend, waarop het adres geldig is/was en actief. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Order Status Modifier Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Advanced Beneficiary Notice Override Reason Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Filler's Expected Availability Date/Time The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Confidentiality Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Order Type Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Enterer Authorization Mode Sequence of characters (the code) that uniquely identifies the item being referenced by the CNE.2. Different coding schemes will have different elements here. Usage Note: The identifier is required and must be a valid code. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Its data type is string (ST). This is the corresponding text assigned by the coding system to the identifier. Usage Note: Text description of code is optional but its use should be encouraged since it makes messages easier to review for accuracy, especially during interface testing and debugging. Each coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes, and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CNE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. Usage Note: The Coding system must either be present and have a value from the set of allowed coding systems or if not present it will be interpreted to have the same meaning as if it had been valued with the code meaning "HL7 coding system". Refer to HL7 Table 0396 in section 2.17.5 for valid values. Analogous to "Identifier" in component 1. Usage Notes: The Alternate Identifier is used to represent the local or user seen code as described. If present, it obeys the same rules of use and interpretation as described for component 1. If both are present, the identifiers in component 4 and component 1 should have exactly the same meaning, i.e., they should be exact synonyms. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage notes in section introduction for further description. Usage Notes: If present, component 5 obeys the same rules of use and interpretation as described for component 2. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" in component 3. Refer to HL7 Table 0396 in section 2.17.5 for valid values. Usage Notes: If present, components 6 obeys the same rules of use and interpretation as described for component 3. the version ID for the coding system identified by component 3. It belongs conceptually to components 1-3 and appears here only for reasons of backward compatibility. If the coding system is any system other than an "HL7 coding system," version ID must be valued with an actual version ID. If the coding system is "HL7 coding system," version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. Text description of code is optional but its use should be encouraged since it makes messages easier to review for accuracy, especially during interface testing and debugging. The version ID for the coding system identified by component 6. It belongs conceptually to the group of Alternate components (see note 2.A.6.6) and appears here only for reasons of backward compatibility. Usage Notes: If present, component 8 obeys the same rules of use and interpretation as described for component 7. The original text that was available to an automated process or a human before a specific code was assigned. - Set ID. Dit veld bevat het nummer dat dit segment identificeert binnen het bericht. Bij de eerste keer dat het segment voorkomt, moet het volgnummer 1 zijn, bij de tweede keer is het 2, enzovoorts. Quantity This component specifies the numeric quantity or amount of an entity. This component species the units in which the quantity is expressed. Field-by-field, default units may be defined within the specifications. When the quantity is measured in the default units, the units need not be transmitted. If the quantity is recorded in units different from the default, the units must be transmitted. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Repeat Pattern A code representing the repeat pattern defined by the other components of this data type. Refer to User-defined Table 335 – Repeat Pattern for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Specifies an alignment of the repetition to a calendar (e.g., to distinguish every 30 days from "the 5th of every month"). Refer to HL7 Table 0527 - Calendar Alignment for valid values. Note: The Units of Time in table 0527 are taken from the Unified Code for Units of Measure (UCUM) [http://unitsofmeasure.org]. Used for Calendar aligned repeat patterns to determine the amount of time from the beginning of particular RPT-2 (Calendar Alignment) to the beginning of the phase. If Calendar Alignment is DW (days of week), then this would be the offset from the beginning of the week. If Phase Range Begin Value is populated, but Phase Range End Value is not populated, then this component defines when the period (RPT-5, 6) begins. If both Phase Range Begin Value and Phase Range End Value are populated, then this component defines the earliest point in time at which the period (RPT-5, 6) will begin. The units of measure for this component are derived from the Calendar Alignment value in RPT-2. See Table 0572 for the units of measure associated with a particular calendar alignment. Used for Calendar aligned repeat patterns to determine the amount of time from the beginning of particular RPT-2 (Calendar Alignment) to the end of the phase. If Phase Range End Value is populated, but Phase Range Begin Value is not populated, then this component defines when the timing period (RPT-5, 6) begins. If both Phase Range Begin Value and Phase Range End Value are populated, then this component defines the latest point in time at which the period (RPT-5, 6) will begin. The units of measure for this component are derived from the Calendar Alignment value in RPT-2. See Table 0527 for the units of measure associated with a particular calendar alignment. A time duration specifying the frequency at which the periodic interval repeats. RPT-6 (Period Units) defines the units of time for this component. Defines the units used for RPT-5 (Period Quantity). Constrained to units of time. The codes for unit of measure are specified in the Unified Code for Units of Measure (UCUM) [http://unitsofmeasure.org]. Condition Rule: This component is required if RPT-5 (Period Quantity) is populated. A code that indicates whether the exact timing is up to the party executing the schedule (e.g., to distinguish "every 8 hours" from "3 times a day".) Refer to HL7 Table 0136 – Yes/No Indicator for valid values. Y - exact timing up to party executing schedule. N - exact timing as specified. A code for a common (periodical) activity of daily living. Refer to HL7 Table 0528, Event-Related Period for valid values. An interval that marks the offsets for the beginning, width and end of the event-related periodic interval measured from the time each such event actually occurred. A positive numeric value indicates the amount of time after the event in RPT-8. A negative numeric value indicates the amount of time prior to the event in RPT-8. RPT-10 (Event Offset Units) defines the units of time for this component. Usage Note: This component should not be valued unless there is a value in RPT-8 (Event). Defines the units used for RPT-9 (Event Offset Quantity). Constrained to units of time. The codes for unit of measure are specified in the Unified Code for Units of Measure (UCUM) [http://unitsofmeasure.org]. Condition Rule: This component is required if RPT-9 (Event Offset Quantity) is populated. The General Timing Specification as defined by the Version 3 Data Types document. Explicit Time Relative Time and Units This component specifies the numeric quantity or amount of an entity. This component species the units in which the quantity is expressed. Field-by-field, default units may be defined within the specifications. When the quantity is measured in the default units, the units need not be transmitted. If the quantity is recorded in units different from the default, the units must be transmitted. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Service Duration This component specifies the numeric quantity or amount of an entity. This component species the units in which the quantity is expressed. Field-by-field, default units may be defined within the specifications. When the quantity is measured in the default units, the units need not be transmitted. If the quantity is recorded in units different from the default, the units must be transmitted. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Startdatum/-tijd The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Einddatum/-tijd The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Prioriteit Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Condition text Text instruction Conjunction Occurrence duration This component specifies the numeric quantity or amount of an entity. This component species the units in which the quantity is expressed. Field-by-field, default units may be defined within the specifications. When the quantity is measured in the default units, the units need not be transmitted. If the quantity is recorded in units different from the default, the units must be transmitted. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Total occurrence's Set ID - TQ2 Sequence/Results Flag Related Placer Number The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Related Filler Number The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Related Placer Group Number The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Sequence Condition Code Cyclic Entry/Exit Indicator Sequence Condition Time Interval This component specifies the numeric quantity or amount of an entity. This component species the units in which the quantity is expressed. Field-by-field, default units may be defined within the specifications. When the quantity is measured in the default units, the units need not be transmitted. If the quantity is recorded in units different from the default, the units must be transmitted. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Cyclic Group Maximum Number of Repeats Special Service Request Relationship - Set ID. Dit veld bevat het nummer dat dit segment identificeert binnen het bericht. Bij de eerste keer dat het segment voorkomt, moet het volgnummer 1 zijn, bij de tweede keer is het 2, enzovoorts. Aanvraagnummer (Placer Order Number) van het uitbestedende laboratorium. Om unieke identificatie te kunnen garanderen, is de verwachting dat deze identificatie begint met het driecijferige labid van het lab dat dit nummer heeft uitgedeeld. The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Aanvraagnummer (Filler Order Number) van het inbestedende laboratorium. Om unieke identificatie te kunnen garanderen, is de verwachting dat deze identificatie begint met het driecijferige labid van het lab dat dit nummer heeft uitgedeeld. The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Universal Service Identifier. LOINC code en weergavenaam van het gevraagde onderzoek. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Priority - OBR Dit veld is alleen behouden vanwege backward compatibility. Het wordt niet gebruikt. Voorheen prioriteit (bijv. STAT, ASAP). Deze informatie staat nu in het zesde component van OBR-27 Quantity/timing. Datum van de aanvraag. Dit veld is alleen behouden vanwege backward compatibility. Het wordt niet gebruikt. Voorheen datum van de aanvraag. Deze informatie staat nu in het vierde component van OBR-27 Quantity/timing. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Observation Date/Time The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Observation End Date/Time The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Collection Volume This component specifies the numeric quantity or amount of an entity. This component species the units in which the quantity is expressed. Field-by-field, default units may be defined within the specifications. When the quantity is measured in the default units, the units need not be transmitted. If the quantity is recorded in units different from the default, the units must be transmitted. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Collector Identifier This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Specimen Action Code Danger Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Relevant Clinical Information Specimen Received Date/Time. Dit veld is alleen behouden vanwege backward compatibility. Vanaf versie 2.5, in berichten met het SPM-segment, wordt het gebruik van SPM-18 Specimen Received Datim/Time aanbevolen boven gebruik van dit veld. Voor observaties die een monster vereisen, is de specimen received date/time het werkelijke inlevermoment bij de diagnostische service-aanbieder. Dit veld moet een waarde bevatten als de aanvraag bij een monster hoort, of als de observatie een monster vereieste en het bericht een verslag is. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Specimen Source. Dit veld is alleen behouden vanwege backward compatibility. Vanaf versie 2.5, in berichten met het SPM-segment, wordt het gebruik van SPM Specimen segment aanbevolen boven gebruik van dit veld. Contains the specimen source name or code (as a CWE data type component). (Even in the case of observations whose name implies the source, a source may be required, e.g., blood culture-heart blood.) A nationally recognized coding system is to be used for this field. Valid coding sources for this field include: HL7 table 0487 – Specimen Type (replaces HL7 table 0070 – Specimen source codes) SNOMED, etc. Veterinary medicine may choose the tables supported for the components of this field as decided by their industry. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Identifies an additive introduced to the specimen before or at the time of collection. Refer to HL7 Table 0371 – Additive in chapter 7 for valid values. The table’s values are taken from NCCLS AUTO4. The value set can be extended with user specific values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Describes the method of collection when that information is a part of the order. When the method of collection is logically an observation result, it should be included as a result segment (i.e., OBX segment). This component specifies the body site from which the specimen was obtained. A nationally recognized coding system is to be used for this field. Valid coding sources for this field include: HL7 Table 0163 - Body site SNOMED Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Modifies body site. For example, the site could be antecubital fossa, and the site modifier "right." Refer to HL7 Table 0495 Body Site Modifier for allowed values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Indicates whether the specimen is frozen as part of the collection method. Suggested values are F (Frozen); R (Refrigerated). If the component is blank, the specimen is assumed to be at room temperature. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Indicates the role of the sample. Refer to User-defined Table 0369 – Specimen role for suggested values. Each of these values is normally identifiable by the systems and its components and can influence processing and data management related to the specimen. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Ordering Provider This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Order Callback Phone Number Specifies the telephone number in a predetermined format that includes an optional extension, beeper number and comment. This component has been retained for backward compatibility only as of version 2.3. Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C any text] Note: Because this component has been deprecated a new data type has not been defined to replace the formatted ST. A code that represents a specific use of a telecommunication number. Refer to HL7 Table 0201 - Telecommunication use code for valid values. A code that represents the type of telecommunication equipment. Refer to HL7 Table 0202 - Telecommunication equipment type for valid values. Internationalization note: To make this data type interoperate with CEN’s Telecommunication data attribute group, we allow use of the second component for email addresses. The presence of an email address is specified by the addition of the value NET to the Phone Use Code table, and the type of Internet address is specified with the values Internet and X.400 to the Phone Equipment Type table. When used for an Internet address, the first component of the XTN data type will be null. If the @-sign is being used as a subcomponent delimiter, the HL7 subcomponent escape sequence may be used when encoding an Internet address (see Section Country Code (NM). Country Code Area/City Code Local Number Extension Contains comments with respect to the telephone number. The characters established within a company’s internal telephone system network used as a prefix to the Extension component for internal dialing. Note that the use of Extension Prefix requires that the Extension component be valued and that digits, as well as special characters (e.g., *, #) may be used. The characters established within a company’s internal telephone system used in place of the (external) telephone number to facilitate calling because its length is shorter than that of the telephone number. Note that digits, as well as special characters (e.g., *, #) may be used. An expression of the telephone number as an unparsible string. The phone number was entered as free text and sending system does not know how to parse it. Placer Field 1 Placer Field 2 Filler Field 1 Filler Field 2 Results Rpt/Status Chng - Date/Time The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Charge to Practice The amount and denomination of money associated with the charge code. The first component is a quantity. The second component is the denomination in which the quantity is expressed. The values for the denomination component are those specified in ISO-4217. If the denomination is not specified, MSH-17-country code is used to determine the default. Example: |99.50^USD| where USD is the ISO 4217 code for the U.S. American dollar. The code identifying the charge to the ordering entity for the services performed. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Diagnostic Serv Sect ID Resultaatstatus. Bevat vaste waarde F als de de uitvoering aanvraag is afgerond. Dit is bijvoorbeeld naar verwachting het geval als dit het OBR-segment van een voorgaand resultaat is dat wordt meegestuurd in de aanvraag. Dit veld is gedefinieerd voor andere typen koppelingen (bijv., toxicologie). Deze belangrijke informatie, samen met de informatie in OBR-29-parent, identificeert het OBX-segment van het parent resultaat uniek aan deze aanvraag. De waarde van dit OBX-segment in het parent resultaat is het organisme of chemische soort waarvoor deze battery resultaten geeft. Als de huidige bettery bijvoorbeeld een antimicrobiële gevoeligheid is, bevat het OBX-segment van het parent resultaat het organisme waarop de gevoeligheidstest is uitgevoerd. Deze indirecte koppeling heeft de voorkeur omdat de naam van het organisme in het parent resultaat mogelijk diverse voorlopige waarden heeft voordat deze definitief is. Het derde component kan worden gebruikt voor de naam van het organisme uit het parent resultaat. Het organism zou in dit geval exact zo moeten zijn zoals gekweekt uit de parent.We benadrukken dat dit veld niet het gehele resultaat van de parent aanneemt. Het is alleen bedoeld voor de tekstuele naam van het geïdentificeerde organisme of chemische soort. Dit veld wordt alleen gebruikt als methode voor koppelen met het parent resultaat voor systemen die geen niet-ambigue Observation ID's en sub-ID's kunnen genereren.Dit veld is alleen aanwezig als het parent resultaat wordt geïdentificeerd in OBR-29-parent en de parent meerdere child-aanvragen omvat voor elke van meerdere resultaten. (See HL7v2 hoofdstuk 7 voor meer details over deze koppeling.)Een tweede modus voor deze informatie is een standaard observation result segment (OBX). Als er meer dan één organisme aanwezig is, wordt OBX-4-observation sub-ID gebruikt om deze te onderscheiden. In dit geval, bevat de eerste OBX met subID N een waarde die het Nde micro-organisme identificeert, en elke volgende OBX met subID N bevat gevoeligheidswaarden voor een gegeven anti-microbiële test op dit organisme. Contains the unique identifier of the parent observation as defined in the OBX-3 of the parent result. The value is the same as the OBX-3 of the parent. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Contains the sub-ID of the parent result as defined in the OBX-4 of the parent result. The value is the same as the OBX-4 of the parent. Contains a descriptor of the parent observation value as specified in the OBX-5 of the parent result. As an example, the third component may be used to record the name of the microorganism identified by the parent result directly. The organism in this case should be identified exactly as it is in the parent culture. Quantity/Timing. Dit veld is alleen behouden vanwege backward compatibility.De lezer wordt verwezen naar de TQ1 en TQ2 segmenten beschreven respectievelijk in secties 4.5.4 en 4.5.5.Dit veld bevat informatie over hoeveel services moeten worden uitgevoerd op een bepaald servicemoment en hoe vaak deze moeten worden herhaald en om de duur van de aanvraag vast te leggen. This component specifies the quantity of the service that should be provided at each service interval. For example, if two blood cultures are to be obtained every 4 hours, the quantity would be 2. If three units of blood are to be typed and cross-matched, the quantity would be 3. The default value is 1. When units are required, they can be added, specified by a subcomponent delimiter. Note: The component contains the complex data type CQ and cannot be fully expressed. CQ cannot be legally expressed when embedded within another data type. This component specifies the numeric quantity or amount of an entity. This component species the units in which the quantity is expressed. Field-by-field, default units may be defined within the specifications. When the quantity is measured in the default units, the units need not be transmitted. If the quantity is recorded in units different from the default, the units must be transmitted. Determines the interval between repeated services. The default is one time only. The repeating frequency with which the treatment is to be administered. It is similar to the frequency and SIG code tables used in order entry systems. Refer to User-defined Table 0335 - Repeat pattern for suggested values. The first component may repeat, with repeat values separated by a space. The repeats are interpreted as connected by logical ANDs. Example: Twice per day, every other day: BID QOD Three times per day, Monday Wednesday and Friday: TID QJ135 Because of this syntax, repeat values should never contain blanks. This component explicitly lists the actual times referenced by the code in the first component, in the following format: HHMM,HHMM,HHMM,.… This second component will be used to clarify the first component in cases where the actual times vary within an institution. If the time of the order spans more than a single day, this new component is only practical if the same times of administration occur for each day of the order. If the actual start time of the order (as given by the fourth component of the quantity/timing field) is after the first explicit time, the first administration is taken to be the first explicit time after the start time. In the case where the patient moves to a location having a different set of explicit times, the existing order may be updated with a new quantity/timing field showing the changed explicit times. This component indicates how long the service should continue after it is started. The default is INDEF (do indefinitely). This component is coded as follows: Value Description Comments S<integer> <integer> seconds M<integer> <integer> minutes H<integer> <integer> hours D<integer> <integer> days W<integer> <integer> weeks L<integer> <integer> months X<integer> <integer> times at interval specified in the order. A request for 2 blood cultures Q2H X3 would imply obtaining 2 blood cultures 3 different times at 2-hour intervals for a total of 6 blood cultures. T<integer> at the interval and amount stated until a total of <integer> "DOSAGE" is accumulated. Units would be assumed to be the same as in the QUANTITY field. INDEF do indefinitely - also the default This component may be specified by the orderer, in which case it indicates the earliest date/time at which the services should be started. In many cases, however, the start date/time will be implied or will be defined by other fields in the order record (e.g., urgency ‑ STAT). In such a case, this field will be empty. The filling service will often record a value in this field after receipt of the order, however, and compute an end time on the basis of the start date/time for the filling service’s internal use. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| When filled in by the requester of the service, this component should contain the latest date/time that the service should be performed. If it has not been performed by the specified time, it should not be performed at all. The requester may not always fill in this value, yet the filling service may fill it in on the basis of the instruction it receives and the actual start time. Regardless of the value of the end date/time, the service should be stopped at the earliest of the date/times specified by either the duration or the end date/time. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| This component describes the urgency of the request. The following values are suggested (the default for Priority is R): Value Description Comments S Stat With highest priority A ASAP Fill after S orders R Routine Default P Preop C Callback T Timing critical A request implying that it is critical to come as close as possible to the requested time, e.g., for a trough antimicrobial level. PRN As needed If using the value "T" (timing critical), the degree of criticality can be specified thus: Format: Value Description Comments TS<integer> timing critical within <integer> seconds TM<integer> timing critical within <integer> minutes TH<integer> timing critical within <integer> hours TD<integer> timing critical within <integer> days TW<integer> timing critical within <integer> weeks TL<integer> timing critical within <integer> months For the sequential orders specification, these values specify the time criticality with which the predecessor order must be followed by the given order. The priority component may repeat; separate repeating values with a space. This is a free text component that describes the conditions under which the drug is to be given. For example, PRN pain, or to keep blood pressure below 110. The presence of text in this field should be taken to mean that human review is needed to determine the how and/or when this drug should be given. This component is a full text version of the instruction (optional). This non‑null component indicates that a second timing specification is to follow using the repeat delimiter. Refer to HL7 table 0472 - TQ Conjunction ID for valid values Usage Note: There are many situations, such as the creation of an order for a group of intravenous (IV) solutions, where the sequence of the individual intravenous solutions (each a service in itself) needs to be specified, e.g., hyperalimentation with multi-vitamins in every third bottle. There are other situations where part of the order’s instructions contains a results condition of some type, such as "PRN pain". There is currently a free text "condition" component of ORC-7-quantity/timing, which allows any condition to be specified. However, to support a fully encoded version of order sequencing, or results condition, we have defined in the following paragraphs a 10th component of ORC-7-quantity/timing. The sequencing conditions supported by this 10th component are based on the completion of a predecessor service. Identifies whether sequence conditions or a repeating cycle of orders is defined. Refer to HL7-defined Table 0524 – Sequence condition for valid values. Contains the first component of the placer order number, entity identifier. Contains the second component of the placer order number, namespace ID. Refer to user-defined table 0363 - Assigning Authority for suggested values. Contains the first component of the filler order number, entity identifier. Contains the second component of the filler order number, namespace ID. Refer to user-defined table 0363 - Assigning Authority for suggested values Defines the relationship between the start/end of the related predecessor or successor order and the current order from ORC-2, 3 or 4. The acceptable condition values have the form commonly used in project planning methodologies in the following format: <one of "SS", "EE", "SE", or "ES"> +/- <time>. The first letter stands for start (S) or end (E) of predecessor order, where the predecessor is defined by the placer or filler order number in subcomponents 1,2 or subcomponents 3,4. The second letter stands for the start (S) or end (E) of the successor order, where the successor order is the order containing this quantity/timing specification. The time specifies the interval between the predecessor and successor starts or ends (see following examples). Where <time> is defined as: Example Description Comment S<integer> do for <integer> seconds M<integer> do for <integer> minutes H<integer> do for <integer> hours D<integer> do for <integer> days W<integer> do for <integer> weeks L<integer> do for <integer> months The maximum number of repeats to be used only on cyclic groups. The total number of repeats is constrained by the end date/time of the last repeat or the end date/time of the parent, whichever is first. Contains the next to the last component of the placer order number, universal ID. Contains the last component of the placer order number. Refer to HL7 table 0301 - Universal ID Type for valid values. Contains the next to the last component of the filler order number, universal ID. Contains the last component of the placer order number. Refer to HL7 table 0301 - Universal ID Type for valid values. This component contains the duration for a single performance of a service, e.g., whirlpool twenty minutes three times per day for three days. It is optional within TQ and does not repeat. Note: The component delimiter in this CQ is demoted to a subcomponent delimiter. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. This component contains the total number of occurrences of a service that should result from this order. It is optional within TQ and does not repeat. If both the end date/time and the total occurrences are valued and the occurrences would extend beyond the end date/time, then the end date/time takes precedence. Otherwise the number of occurrences takes precedence. Result Copies To This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Dit veld is gelijk aan ORC-8 Parent. Dit veld relateert een child aan zijn parent wanneer een parent-child relatie van toepassing is. Bijvoorbeeld voor tests die over over voorgaande tests zijn gebaseerd, zoals antimicrobiële gevoeligheidstesten die voortkomen uit bloedkweken, moeten het filler ordernummer van de parent (bloedkweek) hier doorgeven. Het parent-child mechanisme wordt nader omschreven onder de order control field notes (zie HL2v2 Sectie 4.5.1.1.1, "Table notes for order control codes of ORC"). Het is verplicht als de aanvraag een child is. Specifies an identifier assigned to an entity by the placer system. For example, the component might be used to convey the following: placer order number of the parent order the specimen identifier as assigned by the placer. A location identifier assigned (or used by) the placer. The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Specifies an identifier assigned to an entity by the filler system. For example, the component might convey the following: filler order number of the parent order the specimen identifier as assigned by the filler. A location identifier assigned (or used by) the filler. The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Transportation Mode Reason for Study Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Principal Result Interpreter This component specifies the name of the person performing a service. Coded ID according to a user-defined table. If the first component is present, either component 8 or 9, or both 10 and 11, must be valued. This component contains the person's family name in a string format. Used to specify a first name. Second and Further Given Names or Initials Thereof Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. Refer to User-defined Table 0297 - CN ID source for suggested values. Used to delineate the first component. If component 1 is valued, either component 8, or 9, or both 10 and 11, must be valued. See section, 2.A.14.4, "Assigning Authority (HD)" for definition. Refer to User-defined Table 0363 – Assigning authority for suggested values. Assigning Authority is normally expressed as an HD data type, but has been flattened to 3 components here (CNS.9, CNS.10 and CNS.11) in this data type so that it may be fully expressed. Also note that if additional components are added to the HD data type in the future, adjustment will need to be made accordingly to this data type If component 1 is valued, either component 8, or 9, or both 10 and 11, must be valued. If component 1 is valued, either component 8, or 9, or both 10 and 11, must be valued. See section, 2.A.14.4, "Assigning Authority (HD)" for definition. If CNN.11 is valued, this component must be valued. If component 1 is valued, either component 8, or 9, or both 10 and 11, must be valued. See section, 2.A.14.4, "Assigning Authority (HD)" for definition. If this component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values If CNN.10 is valued, this component must be valued. If component 1 is valued, either component 8, or 9, or both 10 and 11, must be valued. This component specifies the starting date and time for when the person is performing the service. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| This component specifies the ending date and time for when the person is performing the service. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| This component specifies the code for the point where patient care is administered. It is conditional on NDL. 9 Person Location Type (e.g., nursing unit or department or clinic). After floor, it is the most general patient location designation. Refer to User-defined Table 0302 - Point of care for suggested values Patient room. After point of care, it is the most general location designation. Refer to User-defined Table 0303 - Room for suggested values. This component specifies the code for the patient's bed. After room, it is the most general location designation. Refer to User-defined Table 0304 - Bed for suggested values. This component is subject to site interpretation but generally describes the highest level physical designation of an institution, medical center or enterprise. It is the most general location designation. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. This component specifies the code for the status or availability of the location. For example, it may convey bed status. Refer to User-defined Table 0306 - Location status for suggested values. Location type is the categorization of the location defined by facility, building, floor, point of care, room or bed. Although not a required field, when used, it may be the only populated field. Usually includes values such as nursing unit, department, clinic, SNF, physician’s office. Refer to User-defined Table 0305 - Person location type for suggested values. This component specifies the code for the building where the person is located. After facility, it is the most general location designation. Refer to User-defined Table 0307 - Building for suggested values. This component specifies the code for the floor where the person is located. After building, it is the most general location designation. Refer to User-defined Table 0308 - Floor for suggested values. Assistant Result Interpreter This component specifies the name of the person performing a service. Coded ID according to a user-defined table. If the first component is present, either component 8 or 9, or both 10 and 11, must be valued. This component contains the person's family name in a string format. Used to specify a first name. Second and Further Given Names or Initials Thereof Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. Refer to User-defined Table 0297 - CN ID source for suggested values. Used to delineate the first component. If component 1 is valued, either component 8, or 9, or both 10 and 11, must be valued. See section, 2.A.14.4, "Assigning Authority (HD)" for definition. Refer to User-defined Table 0363 – Assigning authority for suggested values. Assigning Authority is normally expressed as an HD data type, but has been flattened to 3 components here (CNS.9, CNS.10 and CNS.11) in this data type so that it may be fully expressed. Also note that if additional components are added to the HD data type in the future, adjustment will need to be made accordingly to this data type If component 1 is valued, either component 8, or 9, or both 10 and 11, must be valued. If component 1 is valued, either component 8, or 9, or both 10 and 11, must be valued. See section, 2.A.14.4, "Assigning Authority (HD)" for definition. If CNN.11 is valued, this component must be valued. If component 1 is valued, either component 8, or 9, or both 10 and 11, must be valued. See section, 2.A.14.4, "Assigning Authority (HD)" for definition. If this component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values If CNN.10 is valued, this component must be valued. If component 1 is valued, either component 8, or 9, or both 10 and 11, must be valued. This component specifies the starting date and time for when the person is performing the service. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| This component specifies the ending date and time for when the person is performing the service. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| This component specifies the code for the point where patient care is administered. It is conditional on NDL. 9 Person Location Type (e.g., nursing unit or department or clinic). After floor, it is the most general patient location designation. Refer to User-defined Table 0302 - Point of care for suggested values Patient room. After point of care, it is the most general location designation. Refer to User-defined Table 0303 - Room for suggested values. This component specifies the code for the patient's bed. After room, it is the most general location designation. Refer to User-defined Table 0304 - Bed for suggested values. This component is subject to site interpretation but generally describes the highest level physical designation of an institution, medical center or enterprise. It is the most general location designation. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. This component specifies the code for the status or availability of the location. For example, it may convey bed status. Refer to User-defined Table 0306 - Location status for suggested values. Location type is the categorization of the location defined by facility, building, floor, point of care, room or bed. Although not a required field, when used, it may be the only populated field. Usually includes values such as nursing unit, department, clinic, SNF, physician’s office. Refer to User-defined Table 0305 - Person location type for suggested values. This component specifies the code for the building where the person is located. After facility, it is the most general location designation. Refer to User-defined Table 0307 - Building for suggested values. This component specifies the code for the floor where the person is located. After building, it is the most general location designation. Refer to User-defined Table 0308 - Floor for suggested values. Technician This component specifies the name of the person performing a service. Coded ID according to a user-defined table. If the first component is present, either component 8 or 9, or both 10 and 11, must be valued. This component contains the person's family name in a string format. Used to specify a first name. Second and Further Given Names or Initials Thereof Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. Refer to User-defined Table 0297 - CN ID source for suggested values. Used to delineate the first component. If component 1 is valued, either component 8, or 9, or both 10 and 11, must be valued. See section, 2.A.14.4, "Assigning Authority (HD)" for definition. Refer to User-defined Table 0363 – Assigning authority for suggested values. Assigning Authority is normally expressed as an HD data type, but has been flattened to 3 components here (CNS.9, CNS.10 and CNS.11) in this data type so that it may be fully expressed. Also note that if additional components are added to the HD data type in the future, adjustment will need to be made accordingly to this data type If component 1 is valued, either component 8, or 9, or both 10 and 11, must be valued. If component 1 is valued, either component 8, or 9, or both 10 and 11, must be valued. See section, 2.A.14.4, "Assigning Authority (HD)" for definition. If CNN.11 is valued, this component must be valued. If component 1 is valued, either component 8, or 9, or both 10 and 11, must be valued. See section, 2.A.14.4, "Assigning Authority (HD)" for definition. If this component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values If CNN.10 is valued, this component must be valued. If component 1 is valued, either component 8, or 9, or both 10 and 11, must be valued. This component specifies the starting date and time for when the person is performing the service. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| This component specifies the ending date and time for when the person is performing the service. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| This component specifies the code for the point where patient care is administered. It is conditional on NDL. 9 Person Location Type (e.g., nursing unit or department or clinic). After floor, it is the most general patient location designation. Refer to User-defined Table 0302 - Point of care for suggested values Patient room. After point of care, it is the most general location designation. Refer to User-defined Table 0303 - Room for suggested values. This component specifies the code for the patient's bed. After room, it is the most general location designation. Refer to User-defined Table 0304 - Bed for suggested values. This component is subject to site interpretation but generally describes the highest level physical designation of an institution, medical center or enterprise. It is the most general location designation. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. This component specifies the code for the status or availability of the location. For example, it may convey bed status. Refer to User-defined Table 0306 - Location status for suggested values. Location type is the categorization of the location defined by facility, building, floor, point of care, room or bed. Although not a required field, when used, it may be the only populated field. Usually includes values such as nursing unit, department, clinic, SNF, physician’s office. Refer to User-defined Table 0305 - Person location type for suggested values. This component specifies the code for the building where the person is located. After facility, it is the most general location designation. Refer to User-defined Table 0307 - Building for suggested values. This component specifies the code for the floor where the person is located. After building, it is the most general location designation. Refer to User-defined Table 0308 - Floor for suggested values. Transcriptionist This component specifies the name of the person performing a service. Coded ID according to a user-defined table. If the first component is present, either component 8 or 9, or both 10 and 11, must be valued. This component contains the person's family name in a string format. Used to specify a first name. Second and Further Given Names or Initials Thereof Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. Refer to User-defined Table 0297 - CN ID source for suggested values. Used to delineate the first component. If component 1 is valued, either component 8, or 9, or both 10 and 11, must be valued. See section, 2.A.14.4, "Assigning Authority (HD)" for definition. Refer to User-defined Table 0363 – Assigning authority for suggested values. Assigning Authority is normally expressed as an HD data type, but has been flattened to 3 components here (CNS.9, CNS.10 and CNS.11) in this data type so that it may be fully expressed. Also note that if additional components are added to the HD data type in the future, adjustment will need to be made accordingly to this data type If component 1 is valued, either component 8, or 9, or both 10 and 11, must be valued. If component 1 is valued, either component 8, or 9, or both 10 and 11, must be valued. See section, 2.A.14.4, "Assigning Authority (HD)" for definition. If CNN.11 is valued, this component must be valued. If component 1 is valued, either component 8, or 9, or both 10 and 11, must be valued. See section, 2.A.14.4, "Assigning Authority (HD)" for definition. If this component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values If CNN.10 is valued, this component must be valued. If component 1 is valued, either component 8, or 9, or both 10 and 11, must be valued. This component specifies the starting date and time for when the person is performing the service. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| This component specifies the ending date and time for when the person is performing the service. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| This component specifies the code for the point where patient care is administered. It is conditional on NDL. 9 Person Location Type (e.g., nursing unit or department or clinic). After floor, it is the most general patient location designation. Refer to User-defined Table 0302 - Point of care for suggested values Patient room. After point of care, it is the most general location designation. Refer to User-defined Table 0303 - Room for suggested values. This component specifies the code for the patient's bed. After room, it is the most general location designation. Refer to User-defined Table 0304 - Bed for suggested values. This component is subject to site interpretation but generally describes the highest level physical designation of an institution, medical center or enterprise. It is the most general location designation. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. This component specifies the code for the status or availability of the location. For example, it may convey bed status. Refer to User-defined Table 0306 - Location status for suggested values. Location type is the categorization of the location defined by facility, building, floor, point of care, room or bed. Although not a required field, when used, it may be the only populated field. Usually includes values such as nursing unit, department, clinic, SNF, physician’s office. Refer to User-defined Table 0305 - Person location type for suggested values. This component specifies the code for the building where the person is located. After facility, it is the most general location designation. Refer to User-defined Table 0307 - Building for suggested values. This component specifies the code for the floor where the person is located. After building, it is the most general location designation. Refer to User-defined Table 0308 - Floor for suggested values. Scheduled Date/Time The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Number of Sample Containers * Transport Logistics of Collected Sample Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Collector's Comment * Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Transport Arrangement Responsibility Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Transport Arranged Escort Required Planned Patient Transport Comment Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Procedure Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Procedure Code Modifier Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Placer Supplemental Service Information Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Filler Supplemental Service Information Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Medically Necessary Duplicate Procedure Reason. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Result Handling Universal Service Identifier Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Auto-Dilution Factor Defined as greater than, less than, greater than or equal, less than or equal, equal, and not equal, respectively (= ">" or "<" or ">=" or "<=" or "=" or "<>" If this component is not valued, it defaults to equal ("="). A number. "-" or "+" or "/" or "." or ":" A number or null depending on the measurement. Rerun Dilution Factor Defined as greater than, less than, greater than or equal, less than or equal, equal, and not equal, respectively (= ">" or "<" or ">=" or "<=" or "=" or "<>" If this component is not valued, it defaults to equal ("="). A number. "-" or "+" or "/" or "." or ":" A number or null depending on the measurement. Pre-Dilution Factor Defined as greater than, less than, greater than or equal, less than or equal, equal, and not equal, respectively (= ">" or "<" or ">=" or "<=" or "=" or "<>" If this component is not valued, it defaults to equal ("="). A number. "-" or "+" or "/" or "." or ":" A number or null depending on the measurement. Endogenous Content of Pre-Dilution Diluent Defined as greater than, less than, greater than or equal, less than or equal, equal, and not equal, respectively (= ">" or "<" or ">=" or "<=" or "=" or "<>" If this component is not valued, it defaults to equal ("="). A number. "-" or "+" or "/" or "." or ":" A number or null depending on the measurement. Automatic Repeat Allowed Reflex Allowed Analyte Repeat Status Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. The NTE segment is defined here for inclusion in messages defined in other chapters. It is commonly used for sending notes and comments.The technical committees define the meaning of the NTE segments within the context of the messages in their chapters. For each NTE, the description in the message attribute table should include an indication of the segment associated with the NTE, for example "Notes and Comments for the PID". Set ID. Dit veld bevat het nummer dat dit segment identificeert binnen het bericht. Bij de eerste keer dat het segment voorkomt, moet het volgnummer 1 zijn, bij de tweede keer is het 2, enzovoorts. Dit veld wordt gebruik om de bron van de opmerking te duiden. Deze tabel kan lokaal worden uitgebreid bij implementatie. Zie HL7 Tabel 0105 - Source of comment voor alle geldige waarden. In de context van Lab2Lab en Lab2PublicHealth zijn met name deze belangrijk: LAncillary (filler) department is source of commentUitvoerende (filler) laboratorium is bron van de opmerkingPOrderer (placer) is source of commentAanvragende (placer) laboratorium is bron van de opmerkingOOther system is source of commentAnder systeem (bijv. de oorspronkelijke aanvrager) is bron van de opmerking Dit veld bevat de opmerkingtekst van dit segment.NB: Sinds v2.2 volgt dit veld datatype FT in plaats van TX. Aangezien er geen verschil is tussen datatype FT zonder aanvullende opmaakcommando's en het datatype TX, is deze wijziging backward compatibel met de voorgaande versies. Dit veld bevat een waarde om het type opmerking dat wordt gestuurd te duiden. Zie User-Defined Table 0364 - Comment Type voor voorgestelde waarden.NB: Er bestaat ook al een veld in het NTE-segment voor identificatie van de Sources of Comment (bijv. ancillary, placer, anders). Sommige systemen moet echter ook andere typen opmerkingen kunnen onderscheiden (bijv., instructies, reden, opmerkingen, etc.). Om die reden kan voor ieder type opmerking een apart NTE-segment worden gebruikt (bijv., instructies op de ene NTE en opmerkingen in een andere NTE).De volgende waarden worden door RIVM Type-Ned onderscheiden in resultaatberichten:PI - PatiëntinstructiesAI - Aanvullende instructiesGI - Algemene instructies1R - Primaire reden2R - Secundaire redenGR - Algemene redenRE - OpmerkingDR - Duplicaat/interactie reden Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Contact Role Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Contact Name This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, "FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. This component cannot be fully expressed. Identified as v 2.4 erratum. Retained for backward compatibility only as of v 2.5. Refer to Effective Date and Expiration Date components. This component contains the start and end date/times, which define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 0444 – Name assembly order for valid values. The first date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. Contact Address See section 2.A.67, "SAD – street address" for description of components. This component specifies the street or mailing address of a person or institution. When referencing an institution, this first component is used to specify the institution name. When used in connection with a person, this component specifies the first line of the address. Street Name Dwelling Number Second line of address. In US usage, it qualifies address. Examples: Suite 555 or Fourth Floor. When referencing an institution, this component specifies the street address. This component specifies the city, or district or place where the addressee is located depending upon the national convention for formatting addresses for postal usage. This component specifies the state or province where the addressee is located. State or province should be represented by the official postal service codes for that country. This component specifies the zip or postal code where the addressee is located. Zip or postal codes should be represented by the official codes for that country. In the US, the zip code takes the form 99999[-9999], while the Canadian postal code takes the form A9A9A9, and the Australian Postcode takes the form 9999. This component specifies the country where the addressee is locatedHL7 specifies that the 3-character (alphabetic) form of ISO 3166 be used for the country code. Refer to HL7 Table 0399 – Country code in section 2.15.9.17 for valid values. This component specifies the kind or type of address. Refer to HL7 Table 0190 - Address type for valid values. This component specifies any other geographic designation. It includes county, bioregion, SMSA, etc. A code that represents the county in which the specified address resides. User-defined Table 0289 - County/parish is used as the HL7 identifier for the user-defined table of values for this component. When this component is used to represent the county (or parish), component 8 <other geographic designation> should not duplicate it (i.e., the use of <other geographic designation> to represent the county is allowed only for the purpose of backward compatibility, and should be discouraged in this and future versions of HL7). Allowable values: codes defined by government. A code that represents the census tract in which the specified address resides. User-defined Table 0288 - Census tract is used as the HL7 identifier for the user-defined table of values for this component. Allowable Values: codes defined by government. Different <name/address types> and representations of the same name/address should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: Also note that this new component remains in "alphabetic" representation with each repetition of the fields using these data types. I.e. even though the address may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component cannot be fully expressed. Identified as v 2.4 erratum. Retained for backward compatibility only as of v 2.5. Refer to Effective Date and Expiration Date components. This component contains the start and end date/times, which define the period in which this address was valid. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Contact Location This component specifies the code for the point where patient care is administered. It is conditional on PL.6 Person Location Type (e.g., nursing unit or department or clinic). After floor, it is the most general patient location designation. Refer to User-defined Table 0302 - Point of care for suggested values. This component specifies the code for the patient's room. After point of care, it is the most general person location designation. Refer to User-defined Table 0303 - Room for suggested values. This component specifies the code for the patient's bed. After room, it is the most general person location designation. Refer to User-defined Table 0304 - Bed for suggested values. This component is subject to site interpretation but generally describes the highest level physical designation of an institution, medical center or enterprise. It is the most general person location designation. (See Section 2.A.33, "HD - hierarchic designator") for discussion of data type. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be redefined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. This component specifies the code for the status or availability of the location. For example, it may convey bed status. Refer to User-defined Table 0306 - Location status for suggested values. Person location type is the categorization of the person’s location defined by facility, building, floor, point of care, room or bed. Although not a required field, when used, it may be the only populated field. It usually includes values such as nursing unit, department, clinic, SNF, physician’s office. Refer to User-defined Table 0305 - Person location type for suggested values. Required if known This component specifies the code for the building where the person is located. After facility, it is the most general person location designation. Refer to User-defined Table 0307 - Building for suggested values. This component specifies the code for the floor where the person is located. After building, it is the most general person location designation. Refer to User-defined Table 0308 - Floor for suggested values. This component describes the location in free text. The unique identifier that represents the physical location as a whole without regard for the individual components. This accommodates sites that may have a different method of defining physical units or who may code at a less granular level. For example, point of care, room, and bed may be 1 indivisible code. The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The entity that creates the data for the individual physical location components. If populated, it should be the authority for all components populated. Refer to User-defined Table 0363 – Assigning authority for suggested values for the first sub-component of the HD component, <namespace ID>. This component makes it possible for codes to be differentiated when the field in which this data type is used repeats. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementors may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Contact Communication Information Specifies the telephone number in a predetermined format that includes an optional extension, beeper number and comment. This component has been retained for backward compatibility only as of version 2.3. Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C any text] Note: Because this component has been deprecated a new data type has not been defined to replace the formatted ST. A code that represents a specific use of a telecommunication number. Refer to HL7 Table 0201 - Telecommunication use code for valid values. A code that represents the type of telecommunication equipment. Refer to HL7 Table 0202 - Telecommunication equipment type for valid values. Internationalization note: To make this data type interoperate with CEN’s Telecommunication data attribute group, we allow use of the second component for email addresses. The presence of an email address is specified by the addition of the value NET to the Phone Use Code table, and the type of Internet address is specified with the values Internet and X.400 to the Phone Equipment Type table. When used for an Internet address, the first component of the XTN data type will be null. If the @-sign is being used as a subcomponent delimiter, the HL7 subcomponent escape sequence may be used when encoding an Internet address (see Section Country Code (NM). Country Code Area/City Code Local Number Extension Contains comments with respect to the telephone number. The characters established within a company’s internal telephone system network used as a prefix to the Extension component for internal dialing. Note that the use of Extension Prefix requires that the Extension component be valued and that digits, as well as special characters (e.g., *, #) may be used. The characters established within a company’s internal telephone system used in place of the (external) telephone number to facilitate calling because its length is shorter than that of the telephone number. Note that digits, as well as special characters (e.g., *, #) may be used. An expression of the telephone number as an unparsible string. The phone number was entered as free text and sending system does not know how to parse it. Preferred Method of Contact Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Contact Identifiers Specifies the license number or other ID number such as UPIN, Medicare and Medicaid number. Specifies the type of number. Refer to User-defined table 0338 – Practitioner ID Number for suggested values. Specifies the state or province in which the license or ID is valid, if relevant, or other qualifying information. It is recommended that state qualifications use the abbreviations from the postal service of the country. Specifies the date when the license or ID is no longer valid. Set ID - DG1 Diagnosis Coding Method Diagnosis Code - DG1 Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Diagnosis Description Diagnosis Date/Time The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Diagnosis Type Major Diagnostic Category Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Diagnostic Related Group Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. DRG Approval Indicator DRG Grouper Review Code Outlier Type Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Outlier Days Outlier Cost The only required component; usually containing a decimal point. Note that each component of the MO data type (Section 2.A.41, "MO - money") is a subcomponent here. The first component is a quantity. The second component is the denomination in which the quantity is expressed. The values for the denomination component are those specified in ISO-4217. If the denomination is not specified, MSH-17-country code is used to determine the default. Example: |99.50^USD| where USD is the ISO 4217 code for the U.S. American dollar. A coded value, data type ID. Refer to HL7 Table 0205 - Price type for valid values. Each is a NM data type; together they specify the "range". The range can be defined as either time or quantity. For example, the range can indicate that the first 10 minutes of the procedure has one price. Another repetition of the data type can use the range to specify that the following 10 to 60 minutes of the procedure is charged at another price per; a final repetition can specify that the final 60 to N minutes of the procedure at a third price. Note that, if the <price type> component is TP, both <from value> and <to value> may be null. See <from value> above. A coded value, data type CE, defined by the standard table of units for either time or quantity (see for example, the tables in Section 7.1.4, "Coding schemes"). This describes the units associated with the range, e.g., seconds, minutes, hours, days, quantity (i.e., count); it is required if <from value> and <to value> are present. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Refer to HL7 Table 0298 - CP range type for valid values. Grouper Version And Type Diagnosis Priority Diagnosing Clinician This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Diagnosis Classification Confidential Indicator Attestation Date/Time The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Diagnosis Identifier The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Diagnosis Action Code Vraagstelling - Set ID. Dit veld bevat het nummer dat dit segment identificeert binnen het bericht. Bij de eerste keer dat het segment voorkomt, moet het volgnummer 1 zijn, bij de tweede keer is het 2, enzovoorts. Datatype van de waarde in OBX-5. Indien mogelijk een waarde uit de waardelijst gekoppeld bij OBX-5 en anders in vrije tekst. Observation Identifier. NB: SNOMED CT code 55607006 Problem (finding) Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Observation Sub-ID Observation Value. Indien mogelijk een waarde uit de gekoppelde waardelijst en anders in vrije tekst. Units Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. References Range Abnormal Flags Probability Nature of Abnormal Test Observatieresultaat status Effective Date of Reference Range The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| User Defined Access Checks Date/Time of the Observation The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Producer's ID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Responsible Observer This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Observation Method Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Equipment Instance Identifier The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Date/Time of the Analysis The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Onderliggend lijden - Set ID. Dit veld bevat het nummer dat dit segment identificeert binnen het bericht. Bij de eerste keer dat het segment voorkomt, moet het volgnummer 1 zijn, bij de tweede keer is het 2, enzovoorts. Datatype van de waarde in OBX-5. Observation Identifier. NB: SNOMED CT code uit Zorginformatiebouwsteen Probleem 4.0 - ProbleemTypeCodelijst Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Observation Sub-ID Observation value. Verwachte waarde is een diagnose uit SNOMED CT Units Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. References Range Abnormal Flags Probability Nature of Abnormal Test Observatieresultaat status Effective Date of Reference Range The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| User Defined Access Checks Date/Time of the Observation The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Producer's ID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Responsible Observer This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Observation Method Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Equipment Instance Identifier The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Date/Time of the Analysis The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Gewicht - Set ID. Dit veld bevat het nummer dat dit segment identificeert binnen het bericht. Bij de eerste keer dat het segment voorkomt, moet het volgnummer 1 zijn, bij de tweede keer is het 2, enzovoorts. Datatype van de waarde in OBX-5. Observation Identifier. NB: LOINC code uit Zorginformatiebouwsteen Lichaamsgewicht 3.1 - NL-CM:12.1.2 Gewichtwaarde Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Observation Sub-ID Observation Value. Het gewicht wordt uitgedrukt in kilogram (kg). Bij pasgeborenen onder 3 kg wordt het gewicht veelal in grammen uitgedrukt. Eenheden. Het gewicht wordt uitgedrukt in kilogram (kg). Bij pasgeborenen onder 3 kg wordt het gewicht veelal in grammen uitgedrukt. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. References Range Abnormal Flags Probability Nature of Abnormal Test Observatieresultaat status Effective Date of Reference Range The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| User Defined Access Checks Date/Time of the Observation The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Producer's ID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Responsible Observer This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Observation Method Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Equipment Instance Identifier The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Date/Time of the Analysis The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Lengte - Set ID. Dit veld bevat het nummer dat dit segment identificeert binnen het bericht. Bij de eerste keer dat het segment voorkomt, moet het volgnummer 1 zijn, bij de tweede keer is het 2, enzovoorts. Datatype van de waarde in OBX-5. Observation Identifier. NB: LOINC code uit Zorginformatiebouwsteen Lichaamslengte 3.1 - NL-CM:12.2.2 LengteWaarde Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Observation Sub-ID Observation Value. Lichaamslengte. De eenheid komt in OBX-6. Eenheden. De lengte wordt uitgedrukt in centimeter (cm). Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. References Range Abnormal Flags Probability Nature of Abnormal Test Observatieresultaat status Effective Date of Reference Range The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| User Defined Access Checks Date/Time of the Observation The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Producer's ID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Responsible Observer This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Observation Method Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Equipment Instance Identifier The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Date/Time of the Analysis The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Eerste ziektedag - Set ID. Dit veld bevat het nummer dat dit segment identificeert binnen het bericht. Bij de eerste keer dat het segment voorkomt, moet het volgnummer 1 zijn, bij de tweede keer is het 2, enzovoorts. Datatype van de waarde in OBX-5. Observation Identifier. Gecodeerde identificatie van de test waarvoor OBX-5 het resultaat bevat Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Observation Sub-ID Observation Value. Eerste ziektedag The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Units Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. References Range Abnormal Flags Probability Nature of Abnormal Test Observatieresultaat status Effective Date of Reference Range The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| User Defined Access Checks Date/Time of the Observation The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Producer's ID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Responsible Observer This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Observation Method Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Equipment Instance Identifier The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Date/Time of the Analysis The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Duur van de klacht - Set ID. Dit veld bevat het nummer dat dit segment identificeert binnen het bericht. Bij de eerste keer dat het segment voorkomt, moet het volgnummer 1 zijn, bij de tweede keer is het 2, enzovoorts. Datatype van de waarde in OBX-5. Observation Identifier. Issue: code ontbreekt nog Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Observation Sub-ID Observation Value. Duur van de klacht Observatieresultaat status Units Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. References Range Abnormal Flags Probability Nature of Abnormal Test Effective Date of Reference Range The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| User Defined Access Checks Date/Time of the Observation The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Producer's ID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Responsible Observer This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Observation Method Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Equipment Instance Identifier The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Date/Time of the Analysis The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Zwangerschap: zwanger? - Set ID. Dit veld bevat het nummer dat dit segment identificeert binnen het bericht. Bij de eerste keer dat het segment voorkomt, moet het volgnummer 1 zijn, bij de tweede keer is het 2, enzovoorts. Datatype van de waarde in OBX-5. Observation Identifier. NB: LOINC code uit Zorginformatiebouwsteen Zwanger 3.1 - NL-CM:7.14.2 Zwanger Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Observation Sub-ID Observation Value. Zie HL7 Table 0136 - Yes/No indicator voor geldige waarden Units Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. References Range Abnormal Flags Probability Nature of Abnormal Test Observatieresultaat status Effective Date of Reference Range The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| User Defined Access Checks Date/Time of the Observation The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Producer's ID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Responsible Observer This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Observation Method Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Equipment Instance Identifier The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Date/Time of the Analysis The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Zwangerschap: graviditeit - Set ID. Dit veld bevat het nummer dat dit segment identificeert binnen het bericht. Bij de eerste keer dat het segment voorkomt, moet het volgnummer 1 zijn, bij de tweede keer is het 2, enzovoorts. Datatype van de waarde in OBX-5. Observation Identifier. NB: LOINC code uit Zorginformatiebouwsteen Zwanger 3.1 - NL-CM:7.14.5 Graviditeit Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Observation Sub-ID Observation Value. Graviditeit Units Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. References Range Abnormal Flags Probability Nature of Abnormal Test Observatieresultaat status Effective Date of Reference Range The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| User Defined Access Checks Date/Time of the Observation The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Producer's ID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Responsible Observer This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Observation Method Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Equipment Instance Identifier The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Date/Time of the Analysis The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Zwangerschap: pariteit - Set ID. Dit veld bevat het nummer dat dit segment identificeert binnen het bericht. Bij de eerste keer dat het segment voorkomt, moet het volgnummer 1 zijn, bij de tweede keer is het 2, enzovoorts. Datatype van de waarde in OBX-5. Observation Identifier. NB: LOINC code uit Zorginformatiebouwsteen Zwanger 3.1 - NL-CM:7.14.6 Pariteit Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Observation Sub-ID Observation Value. Pariteit Units Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. References Range Abnormal Flags Probability Nature of Abnormal Test Observatieresultaat status Effective Date of Reference Range The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| User Defined Access Checks Date/Time of the Observation The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Producer's ID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Responsible Observer This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Observation Method Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Equipment Instance Identifier The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Date/Time of the Analysis The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Zwangerschap: a terme datum - Set ID. Dit veld bevat het nummer dat dit segment identificeert binnen het bericht. Bij de eerste keer dat het segment voorkomt, moet het volgnummer 1 zijn, bij de tweede keer is het 2, enzovoorts. Datatype van de waarde in OBX-5. Observation Identifier. NB: LOINC code uit Zorginformatiebouwsteen Zwanger 3.1 - NL-CM:7.14.3 ATermeDatum Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Observation Sub-ID Observation Value. Á terme datum The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Units Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. References Range Abnormal Flags Probability Nature of Abnormal Test Observatieresultaat status Effective Date of Reference Range The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| User Defined Access Checks Date/Time of the Observation The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Producer's ID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Responsible Observer This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Observation Method Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Equipment Instance Identifier The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Date/Time of the Analysis The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Zwangerschap: duur in dagen - Set ID. Dit veld bevat het nummer dat dit segment identificeert binnen het bericht. Bij de eerste keer dat het segment voorkomt, moet het volgnummer 1 zijn, bij de tweede keer is het 2, enzovoorts. Datatype van de waarde in OBX-5. Observation Identifier. Gecodeerde identificatie van de test waarvoor OBX-5 het resultaat bevat Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Observation Sub-ID Observation Value. Zwangerschapsduur in dagen Eenheden (dagen) Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. References Range Abnormal Flags Probability Nature of Abnormal Test Observatieresultaat status Effective Date of Reference Range The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| User Defined Access Checks Date/Time of the Observation The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Producer's ID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Responsible Observer This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Observation Method Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Equipment Instance Identifier The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Date/Time of the Analysis The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Zwangerschap: Relevante medicatie - Set ID. Dit veld bevat het nummer dat dit segment identificeert binnen het bericht. Bij de eerste keer dat het segment voorkomt, moet het volgnummer 1 zijn, bij de tweede keer is het 2, enzovoorts. Datatype van de waarde in OBX-5. Observation Identifier. Type medicatie als G-Standaard Generieke productcode (GPK) of als Handelsproductcode (HPK) Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Observation Sub-ID Observation Value. Dosering van de medicatie in OBX-3 Units Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. References Range Abnormal Flags Probability Nature of Abnormal Test Observatieresultaat status Effective Date of Reference Range The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| User Defined Access Checks Date/Time of the Observation The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Producer's ID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Responsible Observer This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Observation Method Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Equipment Instance Identifier The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Date/Time of the Analysis The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Symptoom De dataset vraagt hier SNOMED CT gecodeerde symptomen en waarden als hoeveelheid zonder de bijbehorende symptomenlijst te coderen. Dit segment gaat uit van de verwachting dat de gevraagde informatie niet gecodeerd en dus alleen als vrije tekst beschikbaar is. Set ID. Dit veld bevat het nummer dat dit segment identificeert binnen het bericht. Bij de eerste keer dat het segment voorkomt, moet het volgnummer 1 zijn, bij de tweede keer is het 2, enzovoorts. Datatype van de waarde in OBX-5. Observation Identifier. NB: SNOMED CT code uit Zorginformatiebouwsteen Probleem 4.0 - ProbleemTypeCodelijst Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Observation Sub-ID Observation Value. Verwachte waarde is een diagnose (uit SNOMED CT) volgens limitatieve lijst. Bv.: Koude rillingen, koorts, braken, diarree, eventueel aangevuld met een bijbehorende waarde zoals "39 °C" Units Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. References Range Abnormal Flags Probability Nature of Abnormal Test Observatieresultaat status Effective Date of Reference Range The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| User Defined Access Checks Date/Time of the Observation The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Producer's ID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Responsible Observer This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Observation Method Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Equipment Instance Identifier The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Date/Time of the Analysis The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Vaccinatiestatus - Set ID. Dit veld bevat het nummer dat dit segment identificeert binnen het bericht. Bij de eerste keer dat het segment voorkomt, moet het volgnummer 1 zijn, bij de tweede keer is het 2, enzovoorts. Datatype van de waarde in OBX-5. Observation Identifier. Type vaccin als G-Standaard Generieke productcode (GPK) of als Handelsproductcode (HPK) KNMP-GPC = Naming of coding system Generieke productcodeKNMP-HPC = Naming of coding system Handelsproductcode Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Observation Sub-ID Observation Value. Vaccinatiestatus datum The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Units Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. References Range Abnormal Flags Probability Nature of Abnormal Test Observatieresultaat status Effective Date of Reference Range The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| User Defined Access Checks Date/Time of the Observation The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Producer's ID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Responsible Observer This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Observation Method Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Equipment Instance Identifier The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Date/Time of the Analysis The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Recente ingrepen - Set ID. Dit veld bevat het nummer dat dit segment identificeert binnen het bericht. Bij de eerste keer dat het segment voorkomt, moet het volgnummer 1 zijn, bij de tweede keer is het 2, enzovoorts. Datatype van de waarde in OBX-5. Observation Identifier. NB: LOINC code uit Zorginformatiebouwsteen Verrichting 4.0 - NL-CM:14.1.1 Verrichting Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Observation Sub-ID Observation Value. Recente ingreep gecodeerd in SNOMED CT indien mogelijk of in vrije tekst The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Units Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. References Range Abnormal Flags Probability Nature of Abnormal Test Observatieresultaat status Effective Date of Reference Range. Recente ingreep datum The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| User Defined Access Checks Date/Time of the Observation The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Producer's ID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Responsible Observer This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Observation Method Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Equipment Instance Identifier The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Date/Time of the Analysis The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Prothetisch materiaal - Set ID. Dit veld bevat het nummer dat dit segment identificeert binnen het bericht. Bij de eerste keer dat het segment voorkomt, moet het volgnummer 1 zijn, bij de tweede keer is het 2, enzovoorts. Datatype van de waarde in OBX-5. Observation Identifier. Gecodeerde identificatie van de test waarvoor OBX-5 het resultaat bevat Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Observation Sub-ID Observation Value. Recente ingreep gecodeerd met SNOMED CT indien mogelijk, anders als vrije tekst Units Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. References Range Abnormal Flags Probability Nature of Abnormal Test Observatieresultaat status Effective Date of Reference Range The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| User Defined Access Checks Date/Time of the Observation The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Producer's ID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Responsible Observer This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Observation Method Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Equipment Instance Identifier The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Date/Time of the Analysis The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Contact met dieren of planten - Set ID. Dit veld bevat het nummer dat dit segment identificeert binnen het bericht. Bij de eerste keer dat het segment voorkomt, moet het volgnummer 1 zijn, bij de tweede keer is het 2, enzovoorts. Datatype van de waarde in OBX-5. Observation Identifier. Gecodeerde identificatie van de test waarvoor OBX-5 het resultaat bevat Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Observation Sub-ID Observation Value Units Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. References Range Abnormal Flags Probability Nature of Abnormal Test Observatieresultaat status Effective Date of Reference Range The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| User Defined Access Checks Date/Time of the Observation The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Producer's ID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Responsible Observer This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Observation Method Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Equipment Instance Identifier The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Date/Time of the Analysis The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Externe factor: Verblijf in buitenland / Externe factor: Ziekenhuisopname buitenland - Set ID. Dit veld bevat het nummer dat dit segment identificeert binnen het bericht. Bij de eerste keer dat het segment voorkomt, moet het volgnummer 1 zijn, bij de tweede keer is het 2, enzovoorts. Datatype van de waarde in OBX-5. Observation Identifier. Gecodeerde identificatie van de test waarvoor OBX-5 het resultaat bevat Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Observation Sub-ID Land, gebied en periode van/tot in vrije tekst Units Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. References Range Abnormal Flags Probability Nature of Abnormal Test Observatieresultaat status Effective Date of Reference Range The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| User Defined Access Checks Date/Time of the Observation The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Producer's ID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Responsible Observer This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Observation Method Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Equipment Instance Identifier The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Date/Time of the Analysis The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| - Set ID. Dit veld bevat het nummer dat dit segment identificeert binnen het bericht. Bij de eerste keer dat het segment voorkomt, moet het volgnummer 1 zijn, bij de tweede keer is het 2, enzovoorts. Source of Comment Externe factor ziekenhuisopname buitenland in vrije tekst Type opmerking Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Externe factor: beroep - Set ID. Dit veld bevat het nummer dat dit segment identificeert binnen het bericht. Bij de eerste keer dat het segment voorkomt, moet het volgnummer 1 zijn, bij de tweede keer is het 2, enzovoorts. Datatype van de waarde in OBX-5. Observation Identifier. Gecodeerde identificatie van de test waarvoor OBX-5 het resultaat bevat Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Observation Sub-ID Beroep in vrije tekst Units Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. References Range Abnormal Flags Probability Nature of Abnormal Test Observatieresultaat status Effective Date of Reference Range The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| User Defined Access Checks Date/Time of the Observation The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Producer's ID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Responsible Observer This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Observation Method Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Equipment Instance Identifier The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Date/Time of the Analysis The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Resultaat sneltest - Set ID. Dit veld bevat het nummer dat dit segment identificeert binnen het bericht. Bij de eerste keer dat het segment voorkomt, moet het volgnummer 1 zijn, bij de tweede keer is het 2, enzovoorts. Datatype van de waarde in OBX-5. Observation Identifier. Gecodeerde identificatie van de test waarvoor OBX-5 het resultaat bevat Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Observation Sub-ID Observation Value Units Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. References Range Abnormal Flags Probability Nature of Abnormal Test Observatieresultaat status Effective Date of Reference Range The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| User Defined Access Checks Date/Time of the Observation The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Producer's ID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Responsible Observer This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Observation Method Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Equipment Instance Identifier The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Date/Time of the Analysis The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Gevraagd onderzoek Set ID. Dit veld bevat het nummer dat dit segment identificeert binnen het bericht. Bij de eerste keer dat het segment voorkomt, moet het volgnummer 1 zijn, bij de tweede keer is het 2, enzovoorts. Datatype van de waarde in OBX-5. Observation Identifier. Gecodeerde identificatie van de test waarvoor OBX-5 het resultaat bevat Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Observation Sub-ID Observation value. Resultaatwaarde bij de test die is geïdentificeerd in OBX-3, volgens het datatype dat staat in OBX-2. Eventuele eenheden komen in OBX-6 Units Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. References Range Abnormal Flags Probability Nature of Abnormal Test Observatieresultaat status Effective Date of Reference Range The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| User Defined Access Checks Date/Time of the Observation The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Producer's ID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Responsible Observer This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Observation Method Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Equipment Instance Identifier The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Date/Time of the Analysis The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Universal Service Identifier Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Auto-Dilution Factor Defined as greater than, less than, greater than or equal, less than or equal, equal, and not equal, respectively (= ">" or "<" or ">=" or "<=" or "=" or "<>" If this component is not valued, it defaults to equal ("="). A number. "-" or "+" or "/" or "." or ":" A number or null depending on the measurement. Rerun Dilution Factor Defined as greater than, less than, greater than or equal, less than or equal, equal, and not equal, respectively (= ">" or "<" or ">=" or "<=" or "=" or "<>" If this component is not valued, it defaults to equal ("="). A number. "-" or "+" or "/" or "." or ":" A number or null depending on the measurement. Pre-Dilution Factor Defined as greater than, less than, greater than or equal, less than or equal, equal, and not equal, respectively (= ">" or "<" or ">=" or "<=" or "=" or "<>" If this component is not valued, it defaults to equal ("="). A number. "-" or "+" or "/" or "." or ":" A number or null depending on the measurement. Endogenous Content of Pre-Dilution Diluent Defined as greater than, less than, greater than or equal, less than or equal, equal, and not equal, respectively (= ">" or "<" or ">=" or "<=" or "=" or "<>" If this component is not valued, it defaults to equal ("="). A number. "-" or "+" or "/" or "." or ":" A number or null depending on the measurement. Automatic Repeat Allowed Reflex Allowed Analyte Repeat Status Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. The NTE segment is defined here for inclusion in messages defined in other chapters. It is commonly used for sending notes and comments.The technical committees define the meaning of the NTE segments within the context of the messages in their chapters. For each NTE, the description in the message attribute table should include an indication of the segment associated with the NTE, for example "Notes and Comments for the PID". Set ID. Dit veld bevat het nummer dat dit segment identificeert binnen het bericht. Bij de eerste keer dat het segment voorkomt, moet het volgnummer 1 zijn, bij de tweede keer is het 2, enzovoorts. Dit veld wordt gebruik om de bron van de opmerking te duiden. Deze tabel kan lokaal worden uitgebreid bij implementatie. Zie HL7 Tabel 0105 - Source of comment voor alle geldige waarden. In de context van Lab2Lab en Lab2PublicHealth zijn met name deze belangrijk: LAncillary (filler) department is source of commentUitvoerende (filler) laboratorium is bron van de opmerkingPOrderer (placer) is source of commentAanvragende (placer) laboratorium is bron van de opmerkingOOther system is source of commentAnder systeem (bijv. de oorspronkelijke aanvrager) is bron van de opmerking Dit veld bevat de opmerkingtekst van dit segment.NB: Sinds v2.2 volgt dit veld datatype FT in plaats van TX. Aangezien er geen verschil is tussen datatype FT zonder aanvullende opmaakcommando's en het datatype TX, is deze wijziging backward compatibel met de voorgaande versies. Dit veld bevat een waarde om het type opmerking dat wordt gestuurd te duiden. Zie User-Defined Table 0364 - Comment Type voor voorgestelde waarden.NB: Er bestaat ook al een veld in het NTE-segment voor identificatie van de Sources of Comment (bijv. ancillary, placer, anders). Sommige systemen moet echter ook andere typen opmerkingen kunnen onderscheiden (bijv., instructies, reden, opmerkingen, etc.). Om die reden kan voor ieder type opmerking een apart NTE-segment worden gebruikt (bijv., instructies op de ene NTE en opmerkingen in een andere NTE).De volgende waarden worden door RIVM Type-Ned onderscheiden in resultaatberichten:PI - PatiëntinstructiesAI - Aanvullende instructiesGI - Algemene instructies1R - Primaire reden2R - Secundaire redenGR - Algemene redenRE - OpmerkingDR - Duplicaat/interactie reden Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Oorspronkelijk patiëntmateriaal waarop het onderzoek plaatsvindt, bijvoorbeeld urine, bloed, sputum. Afgeleid materiaal zoals isolaten, wordt via de (prior) results doorgegeven. Set ID. Dit veld bevat het nummer dat dit segment identificeert binnen het bericht. Bij de eerste keer dat het segment voorkomt, moet het volgnummer 1 zijn, bij de tweede keer is het 2, enzovoorts. Monsternummer Specifies an identifier assigned to an entity by the placer system. For example, the component might be used to convey the following: placer order number of the parent order the specimen identifier as assigned by the placer. A location identifier assigned (or used by) the placer. The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Specifies an identifier assigned to an entity by the filler system. For example, the component might convey the following: filler order number of the parent order the specimen identifier as assigned by the filler. A location identifier assigned (or used by) the filler. The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Specimen Parent IDs Dit veld bevat de identificatie(s) voor het monster of de monsters die hebben bijgedragen aan het monster dat in dit segment wordt aangeduid.Als dit veld wordt herhaald, dan moet SPM-11 Specimen role de waarde "L" (pooled) hebben. De herhalingen van dit veld bevatten de Specimen ID's van de ouder-monsters die aan de set hebben bijgedragen. Gebruiken indien van toepassing Specifies an identifier assigned to an entity by the placer system. For example, the component might be used to convey the following: placer order number of the parent order the specimen identifier as assigned by the placer. A location identifier assigned (or used by) the placer. The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Specifies an identifier assigned to an entity by the filler system. For example, the component might convey the following: filler order number of the parent order the specimen identifier as assigned by the filler. A location identifier assigned (or used by) the filler. The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Materiaaltype. SNOMED CT labcodeset (materiaaltabel) – substance. Gebruiken indien bekend Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Bron (van het materiaal). SNOMED CT labcodeset (materiaaltabel) – identity Gebruiken indien bekend Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Specimen Additives Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Verkrijgwijze van het materiaal. SNOMED CT labcodeset (materiaaltabel) – proc Gebruiken indien bekend Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Herkomst van het materiaal. SNOMED CT labcodeset (materiaaltabel) – topo Gebruiken indien bekend Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Specimen Source Site Modifier Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Morfologie. SNOMED CT labcodeset (materiaaltabel) – morph Gebruiken indien bekend Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Specimen Role Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Hoeveelheid verzameld materiaal. Eenheden worden geacht om UCUM-eenheden te zijn. Gebruik hiervoor de waarde "UCUM" in SPM|12^2&3 Name of Coding System This component specifies the numeric quantity or amount of an entity. This component species the units in which the quantity is expressed. Field-by-field, default units may be defined within the specifications. When the quantity is measured in the default units, the units need not be transmitted. If the quantity is recorded in units different from the default, the units must be transmitted. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Grouped Specimen Count Specimen Description Specimen Handling Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Specimen Risk Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Afnamedatum (materiaal bij patiënt) The first component contains the earliest date/time (time stamp) in the specified range. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Datum dat het materiaal is ingeleverd bij het uitvoerende laboratorium The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Specimen Expiration Date/Time The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Specimen Availability Specimen Reject Reason Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Specimen Quality Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Specimen Appropriateness Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Specimen Condition Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Specimen Current Quantity This component specifies the numeric quantity or amount of an entity. This component species the units in which the quantity is expressed. Field-by-field, default units may be defined within the specifications. When the quantity is measured in the default units, the units need not be transmitted. If the quantity is recorded in units different from the default, the units must be transmitted. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Number of Specimen Containers Container Type Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Container Condition Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Specimen Child Role Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. - Set ID. Dit veld bevat het nummer dat dit segment identificeert binnen het bericht. Bij de eerste keer dat het segment voorkomt, moet het volgnummer 1 zijn, bij de tweede keer is het 2, enzovoorts. Datatype van de waarde in OBX-5. Observation Identifier. Gecodeerde identificatie van de test waarvoor OBX-5 het resultaat bevat Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Observation Sub-ID Aspect van het materiaal Units Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. References Range Abnormal Flags Probability Nature of Abnormal Test Observatieresultaat status Effective Date of Reference Range The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| User Defined Access Checks Date/Time of the Observation The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Producer's ID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Responsible Observer This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Observation Method Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Equipment Instance Identifier The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Date/Time of the Analysis The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| External Accession Identifier The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Accession Identifier The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Container Identifier The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Primary (parent) Container Identifier The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Equipment Container Identifier The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Specimen Source Contains the specimen source name or code (as a CWE data type component). (Even in the case of observations whose name implies the source, a source may be required, e.g., blood culture-heart blood.) A nationally recognized coding system is to be used for this field. Valid coding sources for this field include: HL7 table 0487 – Specimen Type (replaces HL7 table 0070 – Specimen source codes) SNOMED, etc. Veterinary medicine may choose the tables supported for the components of this field as decided by their industry. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Identifies an additive introduced to the specimen before or at the time of collection. Refer to HL7 Table 0371 – Additive in chapter 7 for valid values. The table’s values are taken from NCCLS AUTO4. The value set can be extended with user specific values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Describes the method of collection when that information is a part of the order. When the method of collection is logically an observation result, it should be included as a result segment (i.e., OBX segment). This component specifies the body site from which the specimen was obtained. A nationally recognized coding system is to be used for this field. Valid coding sources for this field include: HL7 Table 0163 - Body site SNOMED Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Modifies body site. For example, the site could be antecubital fossa, and the site modifier "right." Refer to HL7 Table 0495 Body Site Modifier for allowed values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Indicates whether the specimen is frozen as part of the collection method. Suggested values are F (Frozen); R (Refrigerated). If the component is blank, the specimen is assumed to be at room temperature. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Indicates the role of the sample. Refer to User-defined Table 0369 – Specimen role for suggested values. Each of these values is normally identifiable by the systems and its components and can influence processing and data management related to the specimen. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Registration Date/Time The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Container Status Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Carrier Type Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Carrier Identifier The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Position in Carrier Value1 Value2 Value3 Value4 Tray Type - SAC Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Tray Identifier The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Position in Tray Value1 Value2 Value3 Value4 Location Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Container Height Container Diameter Barrier Delta Bottom Delta Container Height/Diameter/Delta Units Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Container Volume Available Specimen Volume Initial Specimen Volume Volume Units Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Separator Type Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Cap Type Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Additive Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Specimen Component Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Dilution Factor Defined as greater than, less than, greater than or equal, less than or equal, equal, and not equal, respectively (= ">" or "<" or ">=" or "<=" or "=" or "<>" If this component is not valued, it defaults to equal ("="). A number. "-" or "+" or "/" or "." or ":" A number or null depending on the measurement. Treatment Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Temperature Defined as greater than, less than, greater than or equal, less than or equal, equal, and not equal, respectively (= ">" or "<" or ">=" or "<=" or "=" or "<>" If this component is not valued, it defaults to equal ("="). A number. "-" or "+" or "/" or "." or ":" A number or null depending on the measurement. Hemolysis Index Hemolysis Index Units Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Lipemia Index Lipemia Index Units Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Icterus Index Icterus Index Units Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Fibrin Index Fibrin Index Units Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. System Induced Contaminants Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Drug Interference Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Artificial Blood Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Special Handling Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Other Environmental Factors Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. - Set ID. Dit veld bevat het nummer dat dit segment identificeert binnen het bericht. Bij de eerste keer dat het segment voorkomt, moet het volgnummer 1 zijn, bij de tweede keer is het 2, enzovoorts. Waarde type. Geeft gecodeerd aan welk datatype de waarde in OBX-5 heeft. Waardelijst met de belangrijkste waarden: CNE – coded with no exceptions, bv. voor SNOMED CT organismecode. Waardelijst is de labcodeset.NM – numeric, bv voor diameterSN – structured numeric, bv voor MIC waarde. Via IHE Lab: In oudere versies van HL7 werd hiervoor nog datatype ST gebruikt.TM – tijd. Via IHE Lab: voor observatiewaarden die bestaan uit een tijdbepaling (bijv. bloedingtijd) heeft het TM Value Type de voorkeur boven NM maar dit is niet verplicht gesteld. ST – string data, bv voor MIC waarde (vanwege backward compatibiliteit: voorkeur heeft SN) Observation Identifier. LOINC gecodeerde identificatie conform de Nederlandse labcodeset, van de test waarvoor OBX-5 het resultaat bevat Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Observation Sub-ID. Isolaatvolgnummer (in geval dit een identificatie van een micro-organisme betreft). Via IHE Lab: Dit veld wordt gebruikt om verschil te kunnen maken tussen meerdere OBX-segmenten met hetzelfde Observation ID onder dezelfde OBR. Dit veld is verplicht in twee situaties: In een resultaatbericht (ORU of OUL) waar het OBR-segment de resultaten van een microbiologiekweek rapporteert, moet de Observation Sub-ID van ieder gerelateerd OBX-segment zijn gevuld.In een aanvraag (OML) of resultaat (ORU, OUL) bericht met observaties, indien er onder een OBR meer dan één observatie voor dezelfde Observation Identifier (OBX-3) bestaat, dan moeten deze observaties een waarde in OBX-4 bevatten om een unieke combinatie te vormen voor iedere OBX-segment met de waarden in OBX-3 (Observation Identifier) en OBX-4 (Observation Sub-ID).In alle andere situaties is dit veld optioneel. Test resultaat. De waarneming, zoals MIC of diameter of gedetermineerde species. Het datatype wordt bepaald door OBX-2. Units. Eenheid van de meetwaarde volgens UCUM indien van toepassing. Waardelijst is de labcodeset bij de observatiecode in OBX-3. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Referentiewaardebereik Interpretatie van de meting. Waardelijst van de belangrijkste codes voor microbiologie: S - susceptibleI - intermediateR - resistentPOS - positiveNEG - negativeIND - indeterminateSYN-R - Synergy ResistantSYN-S - Synergy Susceptible Verplicht indien bekend Probability Nature of Abnormal Test Observation Result Status. Tenzij lokaal anders afgesproken worden alleen definitieve/gevalideerde resultaten verstuurd. De vaste waarde is dan F. Effective Date of Reference Range The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| User Defined Access Checks Datum en tijd van de waarneming. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Producer's ID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Responsible Observer This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Observation Method Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Equipment Instance Identifier The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Date/Time of the Analysis The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Relevant om testen die door het uitbestedende laboratorium zijn uitgevoerd mee te sturen. Voorbeeld: bij de aanmelding van een materiaal voor typering, bijv CPE binnen Type-Ned, wordt gevraagd om de reeds bekende, door het uitbestedende lab reeds uitgevoerde testen mee te sturen. Op basis hiervan wordt bijvoorbeeld bepaald of het isolaat voor typering in aanmerking komt.  Berichten die voor volksgezondheidsdoeleinden naar RIVM worden gestuurd, moeten worden worden geanonimiseerd. De plaats waar deze anonimisatie van vooral PID-3 en PID-5 plaatsvindt, bij de zender of door een Trusted Third Party (TTP) tussen zender en het RIVM is op basis van lokale afspraken. In berichten die geanonimiseerd dienen te worden/zijn, dienen PID-12 en hoger om privacyredenen geen waarde te bevatten. De normale verwachting is dat het PID-segment terugkomt zoals het is ingestuurd. Na anonimisatie kan dat niet, omdat deze niet omkeerbaar is. Alhoewel het denkbaar is dat in berichten die teruggaan naar de aanvrager, zoals een ORL of een OUL, dan de geanonimiseerde versie van het PID-segment terugkomt, is hiervoor niet gekozen. De verwachting bij dit type berichten is dan ook dat ontvangers matchen op ordernummers/materiaalnummers en niet op PID-gegevens. Het PID-segment met velden PID-3 Patient Identifier List en PID-5 Patient Name, is echter wel verplicht in het bericht. Zie het voorbeeld "minimale vulling in retourberichten", voor hoe het PID-segment er in berichten aan de aanvrager uit dient te zien wanneer een echo van het segment uit de aanvraag niet mogelijk is. Set ID. Dit veld bevat het nummer dat dit segment identificeert binnen het bericht. Bij de eerste keer dat het segment voorkomt, moet het volgnummer 1 zijn, bij de tweede keer is het 2, enzovoorts. Patient ID The value of the identifier itself. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. The algorithm for calculating a Mod10 check digit is as follows: Assume you have an identifier - 12345. Take the odd digit positions, counting from the right, i.e., 531, multiply this number by 2 to get 1062. Take the even digit positions, starting from the right (i.e., 42), prepend these to the 1062 to get 421062. Add all of these six digits together to get 15. Subtract this number from the next highest multiple of 10, i.e., 20 - 15 to get 5. The Mod10 check digit is 5. The Mod10 check digit for 401 is 0; for 9999, it’s 4; for 99999999, it’s 8. The algorithm for calculating a Mod11 check digit is as follows: Terms d = digit of number starting from units digit, followed by 10’s position, followed by 100’s position, etc. w = weight of digit position starting with the units position, followed by 10’s position, followed by 100’s position etc. Values for w = 2, 3, 4, 5, 6, 7, 2, 3, 4, 5, 6, 7, etc. (repeats for each group of 6 digits) c = check digit Calculation (Step 1) m = sum of (d * w) for positions 1, 2, etc. starting with units digit for d = digit value starting with units position to highest order for w = weight value from 2 to 7 for every six positions starting with units digit (Step 2) c1 = m mod 11 (Step 3) if c1 = 0 then reset c1 = 1 (Step 4) = (11 - c1) mod 10 Example: If the number is 1234567, then the mod 11 check digit = 4 The calculations are: M = (7*2)+(6*3)+(5*4)+(4*5)+(3*6)+(2*7)+(1*2) = 14 + 18 + 20 + 20 + 18 + 14 + 2 = 106 c1 = 106 mod 11 = 7 c = (11-c1) mod 10 = 4 mod 10 = 4 Other variants of these check digit algorithms exist and may be used by local bilateral site agreement. Note: The check digit and code identifying check digit scheme are null if ID is alphanumeric. The assigning authority is a unique name of the system (or organization or agency or department) that creates the data. . Refer to User-defined Table 0363 – Assigning authority for suggested values. The reader is referred to the CX.9 and the CX.10 if there is a need to transmit values with semantic meaning for an assigning jurisdiction or assigning department or agency in addition to, or instead of, an assigning authority. However, all 3 components may be valued. If, in so doing, it is discovered that the values in CX.9 and/or CX.10 conflict with CX.4, the user would look to the Message Profile or other implementation agreement for a statement as to which takes precedence. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the patient. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component), may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The first date, if known, on which the identifier is valid and active. The last date, if known, on which the identifier is valid and active. The geo-political body that assigned the identifier in component 1. Refer to HL7 Table 0399 Country Code in section 2.15.9.17 for valid values if the administrative unit under whose jurisdiction the identifier was issued is a country. Refer to User-Defined Table 0347 State/Province for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a state or province. This table is country specific. In the US postal codes may be used. Refer to User-defined Table –0289 County/Parish for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a county or parish. The reader is referred to the CX.4, if there is a need to transmit this information as an OID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. Refer to User-defined Table –0530 Organizations, Agency, Department for suggested values if the administrative unit under whose jurisdiction the identifier was issued is an organization, agency or department. This is populated with site-specific assigning authorities. It also should contain national or international codes when CX-5 Identifier Type may be assigned by more than one authority within a governmental or organizational unit. For example, a federal government may have 2 departments that assign a military identifier, its Veterans Affairs department and its department of defense. It is not recommended to include values for entities such as Social Security Administration (SSA), Immigration and Naturalization Service (INS), Center for Medicare and Medicaid Services (CMS) because they are included in the identifier type table. In these cases the name of the country plus the identifier type yields the correct interpretation of the identifier in component one. Likewise, entries like department of motor vehicles (DMV) and licensing boards are not recommended for inclusion because the combination of state and identifier type yields the correct interpretation of the identifier in component one. This approach is not to be confused with the detailed information provided in the chapter 15 segments that have provision for specifying the precise granting body and issuing body information needed in personnel management messages. Example 1: <Identifier> plus <Visa> yields a unique identifier. Example 2: <Identifier> plus <state> plus <DLN> yields a unique driver’s license number. Example 3: <Identifier> plus <country> plus <INS> yields a unique immigration number. The reader is referred to the CX.4, if there is a need to transmit this information as an OID. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Lijst van patiëntidentificaties. Er worden maximaal slechts twee typen identificatie ondersteund in dit herhalende veld: het burgerservicenummer en het interne patiëntnummer zoals bekend bij de aanvrager. Aanname is dat als het burgerservicenummer ontbreekt in het bericht, deze dan bij aanvragen niet bekend, of niet geverifieerd was.In het geval van anonimisatie bevat het eerste subveld na anonimisatie de uitkomst van het algoritme, het vierde subveld de Assigning authority en het vijfde subveld Identifier type code de vaste waarde "ANON-" (Anonymous identifier) + de oorspronkelijke waarde vóór anonimisatie. The value of the identifier itself. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. The algorithm for calculating a Mod10 check digit is as follows: Assume you have an identifier - 12345. Take the odd digit positions, counting from the right, i.e., 531, multiply this number by 2 to get 1062. Take the even digit positions, starting from the right (i.e., 42), prepend these to the 1062 to get 421062. Add all of these six digits together to get 15. Subtract this number from the next highest multiple of 10, i.e., 20 - 15 to get 5. The Mod10 check digit is 5. The Mod10 check digit for 401 is 0; for 9999, it’s 4; for 99999999, it’s 8. The algorithm for calculating a Mod11 check digit is as follows: Terms d = digit of number starting from units digit, followed by 10’s position, followed by 100’s position, etc. w = weight of digit position starting with the units position, followed by 10’s position, followed by 100’s position etc. Values for w = 2, 3, 4, 5, 6, 7, 2, 3, 4, 5, 6, 7, etc. (repeats for each group of 6 digits) c = check digit Calculation (Step 1) m = sum of (d * w) for positions 1, 2, etc. starting with units digit for d = digit value starting with units position to highest order for w = weight value from 2 to 7 for every six positions starting with units digit (Step 2) c1 = m mod 11 (Step 3) if c1 = 0 then reset c1 = 1 (Step 4) = (11 - c1) mod 10 Example: If the number is 1234567, then the mod 11 check digit = 4 The calculations are: M = (7*2)+(6*3)+(5*4)+(4*5)+(3*6)+(2*7)+(1*2) = 14 + 18 + 20 + 20 + 18 + 14 + 2 = 106 c1 = 106 mod 11 = 7 c = (11-c1) mod 10 = 4 mod 10 = 4 Other variants of these check digit algorithms exist and may be used by local bilateral site agreement. Note: The check digit and code identifying check digit scheme are null if ID is alphanumeric. The assigning authority is a unique name of the system (or organization or agency or department) that creates the data. . Refer to User-defined Table 0363 – Assigning authority for suggested values. The reader is referred to the CX.9 and the CX.10 if there is a need to transmit values with semantic meaning for an assigning jurisdiction or assigning department or agency in addition to, or instead of, an assigning authority. However, all 3 components may be valued. If, in so doing, it is discovered that the values in CX.9 and/or CX.10 conflict with CX.4, the user would look to the Message Profile or other implementation agreement for a statement as to which takes precedence. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the patient. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component), may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The first date, if known, on which the identifier is valid and active. The last date, if known, on which the identifier is valid and active. The geo-political body that assigned the identifier in component 1. Refer to HL7 Table 0399 Country Code in section 2.15.9.17 for valid values if the administrative unit under whose jurisdiction the identifier was issued is a country. Refer to User-Defined Table 0347 State/Province for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a state or province. This table is country specific. In the US postal codes may be used. Refer to User-defined Table –0289 County/Parish for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a county or parish. The reader is referred to the CX.4, if there is a need to transmit this information as an OID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. Refer to User-defined Table –0530 Organizations, Agency, Department for suggested values if the administrative unit under whose jurisdiction the identifier was issued is an organization, agency or department. This is populated with site-specific assigning authorities. It also should contain national or international codes when CX-5 Identifier Type may be assigned by more than one authority within a governmental or organizational unit. For example, a federal government may have 2 departments that assign a military identifier, its Veterans Affairs department and its department of defense. It is not recommended to include values for entities such as Social Security Administration (SSA), Immigration and Naturalization Service (INS), Center for Medicare and Medicaid Services (CMS) because they are included in the identifier type table. In these cases the name of the country plus the identifier type yields the correct interpretation of the identifier in component one. Likewise, entries like department of motor vehicles (DMV) and licensing boards are not recommended for inclusion because the combination of state and identifier type yields the correct interpretation of the identifier in component one. This approach is not to be confused with the detailed information provided in the chapter 15 segments that have provision for specifying the precise granting body and issuing body information needed in personnel management messages. Example 1: <Identifier> plus <Visa> yields a unique identifier. Example 2: <Identifier> plus <state> plus <DLN> yields a unique driver’s license number. Example 3: <Identifier> plus <country> plus <INS> yields a unique immigration number. The reader is referred to the CX.4, if there is a need to transmit this information as an OID. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Alternate Patient ID - PID The value of the identifier itself. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. The algorithm for calculating a Mod10 check digit is as follows: Assume you have an identifier - 12345. Take the odd digit positions, counting from the right, i.e., 531, multiply this number by 2 to get 1062. Take the even digit positions, starting from the right (i.e., 42), prepend these to the 1062 to get 421062. Add all of these six digits together to get 15. Subtract this number from the next highest multiple of 10, i.e., 20 - 15 to get 5. The Mod10 check digit is 5. The Mod10 check digit for 401 is 0; for 9999, it’s 4; for 99999999, it’s 8. The algorithm for calculating a Mod11 check digit is as follows: Terms d = digit of number starting from units digit, followed by 10’s position, followed by 100’s position, etc. w = weight of digit position starting with the units position, followed by 10’s position, followed by 100’s position etc. Values for w = 2, 3, 4, 5, 6, 7, 2, 3, 4, 5, 6, 7, etc. (repeats for each group of 6 digits) c = check digit Calculation (Step 1) m = sum of (d * w) for positions 1, 2, etc. starting with units digit for d = digit value starting with units position to highest order for w = weight value from 2 to 7 for every six positions starting with units digit (Step 2) c1 = m mod 11 (Step 3) if c1 = 0 then reset c1 = 1 (Step 4) = (11 - c1) mod 10 Example: If the number is 1234567, then the mod 11 check digit = 4 The calculations are: M = (7*2)+(6*3)+(5*4)+(4*5)+(3*6)+(2*7)+(1*2) = 14 + 18 + 20 + 20 + 18 + 14 + 2 = 106 c1 = 106 mod 11 = 7 c = (11-c1) mod 10 = 4 mod 10 = 4 Other variants of these check digit algorithms exist and may be used by local bilateral site agreement. Note: The check digit and code identifying check digit scheme are null if ID is alphanumeric. The assigning authority is a unique name of the system (or organization or agency or department) that creates the data. . Refer to User-defined Table 0363 – Assigning authority for suggested values. The reader is referred to the CX.9 and the CX.10 if there is a need to transmit values with semantic meaning for an assigning jurisdiction or assigning department or agency in addition to, or instead of, an assigning authority. However, all 3 components may be valued. If, in so doing, it is discovered that the values in CX.9 and/or CX.10 conflict with CX.4, the user would look to the Message Profile or other implementation agreement for a statement as to which takes precedence. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the patient. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component), may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The first date, if known, on which the identifier is valid and active. The last date, if known, on which the identifier is valid and active. The geo-political body that assigned the identifier in component 1. Refer to HL7 Table 0399 Country Code in section 2.15.9.17 for valid values if the administrative unit under whose jurisdiction the identifier was issued is a country. Refer to User-Defined Table 0347 State/Province for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a state or province. This table is country specific. In the US postal codes may be used. Refer to User-defined Table –0289 County/Parish for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a county or parish. The reader is referred to the CX.4, if there is a need to transmit this information as an OID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. Refer to User-defined Table –0530 Organizations, Agency, Department for suggested values if the administrative unit under whose jurisdiction the identifier was issued is an organization, agency or department. This is populated with site-specific assigning authorities. It also should contain national or international codes when CX-5 Identifier Type may be assigned by more than one authority within a governmental or organizational unit. For example, a federal government may have 2 departments that assign a military identifier, its Veterans Affairs department and its department of defense. It is not recommended to include values for entities such as Social Security Administration (SSA), Immigration and Naturalization Service (INS), Center for Medicare and Medicaid Services (CMS) because they are included in the identifier type table. In these cases the name of the country plus the identifier type yields the correct interpretation of the identifier in component one. Likewise, entries like department of motor vehicles (DMV) and licensing boards are not recommended for inclusion because the combination of state and identifier type yields the correct interpretation of the identifier in component one. This approach is not to be confused with the detailed information provided in the chapter 15 segments that have provision for specifying the precise granting body and issuing body information needed in personnel management messages. Example 1: <Identifier> plus <Visa> yields a unique identifier. Example 2: <Identifier> plus <state> plus <DLN> yields a unique driver’s license number. Example 3: <Identifier> plus <country> plus <INS> yields a unique immigration number. The reader is referred to the CX.4, if there is a need to transmit this information as an OID. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Patiënt naam. In HL7 een verplicht veld.Bij anonimisatie worden namen verwijderd of geanonimiseerd. In het XPN-7 component “Name Type Code” kan hier de code S (Coded Pseudo-Name to ensure anonymity) worden gebruikt. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, "FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. This component cannot be fully expressed. Identified as v 2.4 erratum. Retained for backward compatibility only as of v 2.5. Refer to Effective Date and Expiration Date components. This component contains the start and end date/times, which define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 0444 – Name assembly order for valid values. The first date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. Mother's Maiden Name This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, "FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. This component cannot be fully expressed. Identified as v 2.4 erratum. Retained for backward compatibility only as of v 2.5. Refer to Effective Date and Expiration Date components. This component contains the start and end date/times, which define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 0444 – Name assembly order for valid values. The first date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. Geboortedatum.Verplicht voor RIVM. Format JJJJMMDD. Na anonimisatie wordt de waarde beperkt tot JJJJMM. Verplicht in aanvraagberichten. Optioneel of null in aanvraag-antwoorden en resultaatberichten The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Administratief geslacht Verplicht in aanvraagberichten. Optioneel of null in aanvraag-antwoorden en resultaatberichten Patient Alias This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, "FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. This component cannot be fully expressed. Identified as v 2.4 erratum. Retained for backward compatibility only as of v 2.5. Refer to Effective Date and Expiration Date components. This component contains the start and end date/times, which define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 0444 – Name assembly order for valid values. The first date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the person name is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. Race Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Patiëntadres.Bij anonimisatie wordt het adres beperkt tot de vier cijfers van de postcode en het land. Voor buitenlandse adressen kan de postcode bij anonimisatie volledig worden verwijderd en blijft alleen de landcode staan. Verplicht in aanvraagberichten. Optioneel of null in aanvraag-antwoorden en resultaatberichten Adres straat - Vanaf versie 2.4 is ‘street address’ een samengesteld datatype, waar in de verschillende onderdelen van het adres in verschillende subcomponenten kunnen worden opgenomen This component specifies the street or mailing address of a person or institution. When referencing an institution, this first component is used to specify the institution name. When used in connection with a person, this component specifies the first line of the address. Street Name Dwelling Number Huisnummertoevoeging Woonplaats Staat of provincie. Meestal niet relevant, maar gebruiken bij plaatsnamen in meerdere provincies zoals Afferden (Gelderland en Limburg) en Bergen (Noord-Holland en Limburg) Postcode, indien een Nederlandse postcode dan zonder spaties dus bijv. 2316XA. Merk op dat de HL7v3 specificatie met een spatie voorschrijft. Er is hier bewust gekozen voor compatibiliteit met de officiële HL7v2.4 NL specificatie. Land Adrestype. Voor het eerste adres moet deze de waarde ‘M’ (mailing) hebben. Andere adressen kunnen ook worden doorgegeven, zoals bijv. huisadres (‘H’), of tijdelijk/verblijfsadres (‘C’). Andere geografische aanduiding. N.v.t. voor Nederlandse adressen County/graafschap code. N.v.t. voor Nederlandse adressen Census tract. N.v.t. voor Nederlandse adressen. Representatiecode adres. N.v.t. voor Nederlandse adressen Adres geldigheidsperiode. Hierin kunnen eventueel de begin- en einddatum worden doorgegeven waarbinnen een adres geldig is. Dit kan bijv. voor tijdelijke adressen relevant zijn. Het is echter gemarkeerd als obsoleet en behouden voor backward compatbility in versie 2.5. Zie in plaats daarvan XAD.13 en XAD.14. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. Geldigheidsdatum. De eerste datum, indien bekend, waarop het adres geldig is/was en actief. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Verloopdatum. De laatste datum, indien bekend, waarop het adres geldig is/was en actief. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| County Code Telefoonnummer - Privé. Dit veld bevat alle telefoonnummers van de patiënt. Het eerste telefoonnummer moet het primaire nummer van de patiënt zijn. (Telecommunication use code ‘PRN’). Als het primaire telefoonnummer niet bekend is, moet een ‘repetition delimiter’ worden gestuurd, voorafgaand aan het eerste telefoonnummer. Merk op dat een mobiel nummer ook een ‘Primary Residence Number’ kan zijn. Specifies the telephone number in a predetermined format that includes an optional extension, beeper number and comment. This component has been retained for backward compatibility only as of version 2.3. Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C any text] Note: Because this component has been deprecated a new data type has not been defined to replace the formatted ST. A code that represents a specific use of a telecommunication number. Refer to HL7 Table 0201 - Telecommunication use code for valid values. A code that represents the type of telecommunication equipment. Refer to HL7 Table 0202 - Telecommunication equipment type for valid values. Internationalization note: To make this data type interoperate with CEN’s Telecommunication data attribute group, we allow use of the second component for email addresses. The presence of an email address is specified by the addition of the value NET to the Phone Use Code table, and the type of Internet address is specified with the values Internet and X.400 to the Phone Equipment Type table. When used for an Internet address, the first component of the XTN data type will be null. If the @-sign is being used as a subcomponent delimiter, the HL7 subcomponent escape sequence may be used when encoding an Internet address (see Section Country Code (NM). Country Code Area/City Code Local Number Extension Contains comments with respect to the telephone number. The characters established within a company’s internal telephone system network used as a prefix to the Extension component for internal dialing. Note that the use of Extension Prefix requires that the Extension component be valued and that digits, as well as special characters (e.g., *, #) may be used. The characters established within a company’s internal telephone system used in place of the (external) telephone number to facilitate calling because its length is shorter than that of the telephone number. Note that digits, as well as special characters (e.g., *, #) may be used. An expression of the telephone number as an unparsible string. The phone number was entered as free text and sending system does not know how to parse it. Telefoonnummer - Zakelijk Specifies the telephone number in a predetermined format that includes an optional extension, beeper number and comment. This component has been retained for backward compatibility only as of version 2.3. Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C any text] Note: Because this component has been deprecated a new data type has not been defined to replace the formatted ST. A code that represents a specific use of a telecommunication number. Refer to HL7 Table 0201 - Telecommunication use code for valid values. A code that represents the type of telecommunication equipment. Refer to HL7 Table 0202 - Telecommunication equipment type for valid values. Internationalization note: To make this data type interoperate with CEN’s Telecommunication data attribute group, we allow use of the second component for email addresses. The presence of an email address is specified by the addition of the value NET to the Phone Use Code table, and the type of Internet address is specified with the values Internet and X.400 to the Phone Equipment Type table. When used for an Internet address, the first component of the XTN data type will be null. If the @-sign is being used as a subcomponent delimiter, the HL7 subcomponent escape sequence may be used when encoding an Internet address (see Section Country Code (NM). Country Code Area/City Code Local Number Extension Contains comments with respect to the telephone number. The characters established within a company’s internal telephone system network used as a prefix to the Extension component for internal dialing. Note that the use of Extension Prefix requires that the Extension component be valued and that digits, as well as special characters (e.g., *, #) may be used. The characters established within a company’s internal telephone system used in place of the (external) telephone number to facilitate calling because its length is shorter than that of the telephone number. Note that digits, as well as special characters (e.g., *, #) may be used. An expression of the telephone number as an unparsible string. The phone number was entered as free text and sending system does not know how to parse it. Primary Language Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Burgerlijke staat Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Religion Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Patient Account Number The value of the identifier itself. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. The algorithm for calculating a Mod10 check digit is as follows: Assume you have an identifier - 12345. Take the odd digit positions, counting from the right, i.e., 531, multiply this number by 2 to get 1062. Take the even digit positions, starting from the right (i.e., 42), prepend these to the 1062 to get 421062. Add all of these six digits together to get 15. Subtract this number from the next highest multiple of 10, i.e., 20 - 15 to get 5. The Mod10 check digit is 5. The Mod10 check digit for 401 is 0; for 9999, it’s 4; for 99999999, it’s 8. The algorithm for calculating a Mod11 check digit is as follows: Terms d = digit of number starting from units digit, followed by 10’s position, followed by 100’s position, etc. w = weight of digit position starting with the units position, followed by 10’s position, followed by 100’s position etc. Values for w = 2, 3, 4, 5, 6, 7, 2, 3, 4, 5, 6, 7, etc. (repeats for each group of 6 digits) c = check digit Calculation (Step 1) m = sum of (d * w) for positions 1, 2, etc. starting with units digit for d = digit value starting with units position to highest order for w = weight value from 2 to 7 for every six positions starting with units digit (Step 2) c1 = m mod 11 (Step 3) if c1 = 0 then reset c1 = 1 (Step 4) = (11 - c1) mod 10 Example: If the number is 1234567, then the mod 11 check digit = 4 The calculations are: M = (7*2)+(6*3)+(5*4)+(4*5)+(3*6)+(2*7)+(1*2) = 14 + 18 + 20 + 20 + 18 + 14 + 2 = 106 c1 = 106 mod 11 = 7 c = (11-c1) mod 10 = 4 mod 10 = 4 Other variants of these check digit algorithms exist and may be used by local bilateral site agreement. Note: The check digit and code identifying check digit scheme are null if ID is alphanumeric. The assigning authority is a unique name of the system (or organization or agency or department) that creates the data. . Refer to User-defined Table 0363 – Assigning authority for suggested values. The reader is referred to the CX.9 and the CX.10 if there is a need to transmit values with semantic meaning for an assigning jurisdiction or assigning department or agency in addition to, or instead of, an assigning authority. However, all 3 components may be valued. If, in so doing, it is discovered that the values in CX.9 and/or CX.10 conflict with CX.4, the user would look to the Message Profile or other implementation agreement for a statement as to which takes precedence. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the patient. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component), may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The first date, if known, on which the identifier is valid and active. The last date, if known, on which the identifier is valid and active. The geo-political body that assigned the identifier in component 1. Refer to HL7 Table 0399 Country Code in section 2.15.9.17 for valid values if the administrative unit under whose jurisdiction the identifier was issued is a country. Refer to User-Defined Table 0347 State/Province for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a state or province. This table is country specific. In the US postal codes may be used. Refer to User-defined Table –0289 County/Parish for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a county or parish. The reader is referred to the CX.4, if there is a need to transmit this information as an OID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. Refer to User-defined Table –0530 Organizations, Agency, Department for suggested values if the administrative unit under whose jurisdiction the identifier was issued is an organization, agency or department. This is populated with site-specific assigning authorities. It also should contain national or international codes when CX-5 Identifier Type may be assigned by more than one authority within a governmental or organizational unit. For example, a federal government may have 2 departments that assign a military identifier, its Veterans Affairs department and its department of defense. It is not recommended to include values for entities such as Social Security Administration (SSA), Immigration and Naturalization Service (INS), Center for Medicare and Medicaid Services (CMS) because they are included in the identifier type table. In these cases the name of the country plus the identifier type yields the correct interpretation of the identifier in component one. Likewise, entries like department of motor vehicles (DMV) and licensing boards are not recommended for inclusion because the combination of state and identifier type yields the correct interpretation of the identifier in component one. This approach is not to be confused with the detailed information provided in the chapter 15 segments that have provision for specifying the precise granting body and issuing body information needed in personnel management messages. Example 1: <Identifier> plus <Visa> yields a unique identifier. Example 2: <Identifier> plus <state> plus <DLN> yields a unique driver’s license number. Example 3: <Identifier> plus <country> plus <INS> yields a unique immigration number. The reader is referred to the CX.4, if there is a need to transmit this information as an OID. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. SSN Number - Patient Driver's License Number - Patient This field contains the driver’s license number. Issuing authority for driver’s license. For state or province refer to official postal codes for that country; for country refer to ISO 3166 for codes. The ISO 3166 table has three separate forms of the country code: HL7 specifies that the 3-character (alphabetic) form be used for the country code. User-defined Table 0333 - Driver’s license issuing authority is used as the HL7 identifier for the user-defined table of values for this component. Expiration date (DT) for driver’s license. Mother's Identifier The value of the identifier itself. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. The algorithm for calculating a Mod10 check digit is as follows: Assume you have an identifier - 12345. Take the odd digit positions, counting from the right, i.e., 531, multiply this number by 2 to get 1062. Take the even digit positions, starting from the right (i.e., 42), prepend these to the 1062 to get 421062. Add all of these six digits together to get 15. Subtract this number from the next highest multiple of 10, i.e., 20 - 15 to get 5. The Mod10 check digit is 5. The Mod10 check digit for 401 is 0; for 9999, it’s 4; for 99999999, it’s 8. The algorithm for calculating a Mod11 check digit is as follows: Terms d = digit of number starting from units digit, followed by 10’s position, followed by 100’s position, etc. w = weight of digit position starting with the units position, followed by 10’s position, followed by 100’s position etc. Values for w = 2, 3, 4, 5, 6, 7, 2, 3, 4, 5, 6, 7, etc. (repeats for each group of 6 digits) c = check digit Calculation (Step 1) m = sum of (d * w) for positions 1, 2, etc. starting with units digit for d = digit value starting with units position to highest order for w = weight value from 2 to 7 for every six positions starting with units digit (Step 2) c1 = m mod 11 (Step 3) if c1 = 0 then reset c1 = 1 (Step 4) = (11 - c1) mod 10 Example: If the number is 1234567, then the mod 11 check digit = 4 The calculations are: M = (7*2)+(6*3)+(5*4)+(4*5)+(3*6)+(2*7)+(1*2) = 14 + 18 + 20 + 20 + 18 + 14 + 2 = 106 c1 = 106 mod 11 = 7 c = (11-c1) mod 10 = 4 mod 10 = 4 Other variants of these check digit algorithms exist and may be used by local bilateral site agreement. Note: The check digit and code identifying check digit scheme are null if ID is alphanumeric. The assigning authority is a unique name of the system (or organization or agency or department) that creates the data. . Refer to User-defined Table 0363 – Assigning authority for suggested values. The reader is referred to the CX.9 and the CX.10 if there is a need to transmit values with semantic meaning for an assigning jurisdiction or assigning department or agency in addition to, or instead of, an assigning authority. However, all 3 components may be valued. If, in so doing, it is discovered that the values in CX.9 and/or CX.10 conflict with CX.4, the user would look to the Message Profile or other implementation agreement for a statement as to which takes precedence. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the patient. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component), may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The first date, if known, on which the identifier is valid and active. The last date, if known, on which the identifier is valid and active. The geo-political body that assigned the identifier in component 1. Refer to HL7 Table 0399 Country Code in section 2.15.9.17 for valid values if the administrative unit under whose jurisdiction the identifier was issued is a country. Refer to User-Defined Table 0347 State/Province for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a state or province. This table is country specific. In the US postal codes may be used. Refer to User-defined Table –0289 County/Parish for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a county or parish. The reader is referred to the CX.4, if there is a need to transmit this information as an OID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. Refer to User-defined Table –0530 Organizations, Agency, Department for suggested values if the administrative unit under whose jurisdiction the identifier was issued is an organization, agency or department. This is populated with site-specific assigning authorities. It also should contain national or international codes when CX-5 Identifier Type may be assigned by more than one authority within a governmental or organizational unit. For example, a federal government may have 2 departments that assign a military identifier, its Veterans Affairs department and its department of defense. It is not recommended to include values for entities such as Social Security Administration (SSA), Immigration and Naturalization Service (INS), Center for Medicare and Medicaid Services (CMS) because they are included in the identifier type table. In these cases the name of the country plus the identifier type yields the correct interpretation of the identifier in component one. Likewise, entries like department of motor vehicles (DMV) and licensing boards are not recommended for inclusion because the combination of state and identifier type yields the correct interpretation of the identifier in component one. This approach is not to be confused with the detailed information provided in the chapter 15 segments that have provision for specifying the precise granting body and issuing body information needed in personnel management messages. Example 1: <Identifier> plus <Visa> yields a unique identifier. Example 2: <Identifier> plus <state> plus <DLN> yields a unique driver’s license number. Example 3: <Identifier> plus <country> plus <INS> yields a unique immigration number. The reader is referred to the CX.4, if there is a need to transmit this information as an OID. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Ethnic Group Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Birth Place Meerlingindicator. "Y" indien deze persoon onderdeel is van een meerling. "N" indien dat niet het geval is. Indien dit veld geen waarde bevat, kan hieruit geen meerlingstatus uit worden afgeleid. Verplicht indien bekend in aanvraagberichten. Optioneel of null in aanvraag-antwoorden en resultaatberichten Birth Order Citizenship Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Veterans Military Status Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Nationality Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Patient Death Date and Time The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Patient Death Indicator Identity Unknown Indicator Identity Reliability Code Last Update Date/Time The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Last Update Facility User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Species Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Breed Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Strain Production Class Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Tribal Citizenship Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Living Dependency Living Arrangement Patient Primary Facility The name of the specified organization. A code that represents the type of name i.e., legal name, display name. Refer to User-defined Table 0204 - Organizational Name Type for suggested values. This component has been retained for backward compatibility only as of v 2.5. It is recommended to use component 10 Organization identifier that accommodates alphanumeric identifiers. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. The check digit scheme codes are defined in HL7 Table 0061 - Check digit scheme. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Assigning authorities are unique across a given HL7 implementation. Refer to User-defined Table 0363 - Assigning Authority for suggested values. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e. even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation code for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component contains the sequence of characters (the code) that uniquely identifies the item being referenced by XON.1 Organization Name. This component replaces XON.3 ID Number as of v 2.5. Note: The check digit and code identifying check digit scheme are null if Organization identifier is alphanumeric. Patient Primary Care Provider Name & ID No. This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Student Indicator Handicap Living Will Code Organ Donor Code Separate Bill Duplicate Patient The value of the identifier itself. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. The algorithm for calculating a Mod10 check digit is as follows: Assume you have an identifier - 12345. Take the odd digit positions, counting from the right, i.e., 531, multiply this number by 2 to get 1062. Take the even digit positions, starting from the right (i.e., 42), prepend these to the 1062 to get 421062. Add all of these six digits together to get 15. Subtract this number from the next highest multiple of 10, i.e., 20 - 15 to get 5. The Mod10 check digit is 5. The Mod10 check digit for 401 is 0; for 9999, it’s 4; for 99999999, it’s 8. The algorithm for calculating a Mod11 check digit is as follows: Terms d = digit of number starting from units digit, followed by 10’s position, followed by 100’s position, etc. w = weight of digit position starting with the units position, followed by 10’s position, followed by 100’s position etc. Values for w = 2, 3, 4, 5, 6, 7, 2, 3, 4, 5, 6, 7, etc. (repeats for each group of 6 digits) c = check digit Calculation (Step 1) m = sum of (d * w) for positions 1, 2, etc. starting with units digit for d = digit value starting with units position to highest order for w = weight value from 2 to 7 for every six positions starting with units digit (Step 2) c1 = m mod 11 (Step 3) if c1 = 0 then reset c1 = 1 (Step 4) = (11 - c1) mod 10 Example: If the number is 1234567, then the mod 11 check digit = 4 The calculations are: M = (7*2)+(6*3)+(5*4)+(4*5)+(3*6)+(2*7)+(1*2) = 14 + 18 + 20 + 20 + 18 + 14 + 2 = 106 c1 = 106 mod 11 = 7 c = (11-c1) mod 10 = 4 mod 10 = 4 Other variants of these check digit algorithms exist and may be used by local bilateral site agreement. Note: The check digit and code identifying check digit scheme are null if ID is alphanumeric. The assigning authority is a unique name of the system (or organization or agency or department) that creates the data. . Refer to User-defined Table 0363 – Assigning authority for suggested values. The reader is referred to the CX.9 and the CX.10 if there is a need to transmit values with semantic meaning for an assigning jurisdiction or assigning department or agency in addition to, or instead of, an assigning authority. However, all 3 components may be valued. If, in so doing, it is discovered that the values in CX.9 and/or CX.10 conflict with CX.4, the user would look to the Message Profile or other implementation agreement for a statement as to which takes precedence. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the patient. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component), may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The first date, if known, on which the identifier is valid and active. The last date, if known, on which the identifier is valid and active. The geo-political body that assigned the identifier in component 1. Refer to HL7 Table 0399 Country Code in section 2.15.9.17 for valid values if the administrative unit under whose jurisdiction the identifier was issued is a country. Refer to User-Defined Table 0347 State/Province for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a state or province. This table is country specific. In the US postal codes may be used. Refer to User-defined Table –0289 County/Parish for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a county or parish. The reader is referred to the CX.4, if there is a need to transmit this information as an OID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. Refer to User-defined Table –0530 Organizations, Agency, Department for suggested values if the administrative unit under whose jurisdiction the identifier was issued is an organization, agency or department. This is populated with site-specific assigning authorities. It also should contain national or international codes when CX-5 Identifier Type may be assigned by more than one authority within a governmental or organizational unit. For example, a federal government may have 2 departments that assign a military identifier, its Veterans Affairs department and its department of defense. It is not recommended to include values for entities such as Social Security Administration (SSA), Immigration and Naturalization Service (INS), Center for Medicare and Medicaid Services (CMS) because they are included in the identifier type table. In these cases the name of the country plus the identifier type yields the correct interpretation of the identifier in component one. Likewise, entries like department of motor vehicles (DMV) and licensing boards are not recommended for inclusion because the combination of state and identifier type yields the correct interpretation of the identifier in component one. This approach is not to be confused with the detailed information provided in the chapter 15 segments that have provision for specifying the precise granting body and issuing body information needed in personnel management messages. Example 1: <Identifier> plus <Visa> yields a unique identifier. Example 2: <Identifier> plus <state> plus <DLN> yields a unique driver’s license number. Example 3: <Identifier> plus <country> plus <INS> yields a unique immigration number. The reader is referred to the CX.4, if there is a need to transmit this information as an OID. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Publicity Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Protection Indicator Protection Indicator Effective Date Place of Worship The name of the specified organization. A code that represents the type of name i.e., legal name, display name. Refer to User-defined Table 0204 - Organizational Name Type for suggested values. This component has been retained for backward compatibility only as of v 2.5. It is recommended to use component 10 Organization identifier that accommodates alphanumeric identifiers. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. The check digit scheme codes are defined in HL7 Table 0061 - Check digit scheme. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Assigning authorities are unique across a given HL7 implementation. Refer to User-defined Table 0363 - Assigning Authority for suggested values. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e. even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation code for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component contains the sequence of characters (the code) that uniquely identifies the item being referenced by XON.1 Organization Name. This component replaces XON.3 ID Number as of v 2.5. Note: The check digit and code identifying check digit scheme are null if Organization identifier is alphanumeric. Advance Directive Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Immunization Registry Status Immunization Registry Status Effective Date Publicity Code Effective Date Military Branch Military Rank/Grade Military Status Set ID - PV1 Patient Class Assigned Patient Location This component specifies the code for the point where patient care is administered. It is conditional on PL.6 Person Location Type (e.g., nursing unit or department or clinic). After floor, it is the most general patient location designation. Refer to User-defined Table 0302 - Point of care for suggested values. This component specifies the code for the patient's room. After point of care, it is the most general person location designation. Refer to User-defined Table 0303 - Room for suggested values. This component specifies the code for the patient's bed. After room, it is the most general person location designation. Refer to User-defined Table 0304 - Bed for suggested values. This component is subject to site interpretation but generally describes the highest level physical designation of an institution, medical center or enterprise. It is the most general person location designation. (See Section 2.A.33, "HD - hierarchic designator") for discussion of data type. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be redefined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. This component specifies the code for the status or availability of the location. For example, it may convey bed status. Refer to User-defined Table 0306 - Location status for suggested values. Person location type is the categorization of the person’s location defined by facility, building, floor, point of care, room or bed. Although not a required field, when used, it may be the only populated field. It usually includes values such as nursing unit, department, clinic, SNF, physician’s office. Refer to User-defined Table 0305 - Person location type for suggested values. Required if known This component specifies the code for the building where the person is located. After facility, it is the most general person location designation. Refer to User-defined Table 0307 - Building for suggested values. This component specifies the code for the floor where the person is located. After building, it is the most general person location designation. Refer to User-defined Table 0308 - Floor for suggested values. This component describes the location in free text. The unique identifier that represents the physical location as a whole without regard for the individual components. This accommodates sites that may have a different method of defining physical units or who may code at a less granular level. For example, point of care, room, and bed may be 1 indivisible code. The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The entity that creates the data for the individual physical location components. If populated, it should be the authority for all components populated. Refer to User-defined Table 0363 – Assigning authority for suggested values for the first sub-component of the HD component, <namespace ID>. This component makes it possible for codes to be differentiated when the field in which this data type is used repeats. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementors may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Admission Type Preadmit Number The value of the identifier itself. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. The algorithm for calculating a Mod10 check digit is as follows: Assume you have an identifier - 12345. Take the odd digit positions, counting from the right, i.e., 531, multiply this number by 2 to get 1062. Take the even digit positions, starting from the right (i.e., 42), prepend these to the 1062 to get 421062. Add all of these six digits together to get 15. Subtract this number from the next highest multiple of 10, i.e., 20 - 15 to get 5. The Mod10 check digit is 5. The Mod10 check digit for 401 is 0; for 9999, it’s 4; for 99999999, it’s 8. The algorithm for calculating a Mod11 check digit is as follows: Terms d = digit of number starting from units digit, followed by 10’s position, followed by 100’s position, etc. w = weight of digit position starting with the units position, followed by 10’s position, followed by 100’s position etc. Values for w = 2, 3, 4, 5, 6, 7, 2, 3, 4, 5, 6, 7, etc. (repeats for each group of 6 digits) c = check digit Calculation (Step 1) m = sum of (d * w) for positions 1, 2, etc. starting with units digit for d = digit value starting with units position to highest order for w = weight value from 2 to 7 for every six positions starting with units digit (Step 2) c1 = m mod 11 (Step 3) if c1 = 0 then reset c1 = 1 (Step 4) = (11 - c1) mod 10 Example: If the number is 1234567, then the mod 11 check digit = 4 The calculations are: M = (7*2)+(6*3)+(5*4)+(4*5)+(3*6)+(2*7)+(1*2) = 14 + 18 + 20 + 20 + 18 + 14 + 2 = 106 c1 = 106 mod 11 = 7 c = (11-c1) mod 10 = 4 mod 10 = 4 Other variants of these check digit algorithms exist and may be used by local bilateral site agreement. Note: The check digit and code identifying check digit scheme are null if ID is alphanumeric. The assigning authority is a unique name of the system (or organization or agency or department) that creates the data. . Refer to User-defined Table 0363 – Assigning authority for suggested values. The reader is referred to the CX.9 and the CX.10 if there is a need to transmit values with semantic meaning for an assigning jurisdiction or assigning department or agency in addition to, or instead of, an assigning authority. However, all 3 components may be valued. If, in so doing, it is discovered that the values in CX.9 and/or CX.10 conflict with CX.4, the user would look to the Message Profile or other implementation agreement for a statement as to which takes precedence. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the patient. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component), may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The first date, if known, on which the identifier is valid and active. The last date, if known, on which the identifier is valid and active. The geo-political body that assigned the identifier in component 1. Refer to HL7 Table 0399 Country Code in section 2.15.9.17 for valid values if the administrative unit under whose jurisdiction the identifier was issued is a country. Refer to User-Defined Table 0347 State/Province for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a state or province. This table is country specific. In the US postal codes may be used. Refer to User-defined Table –0289 County/Parish for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a county or parish. The reader is referred to the CX.4, if there is a need to transmit this information as an OID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. Refer to User-defined Table –0530 Organizations, Agency, Department for suggested values if the administrative unit under whose jurisdiction the identifier was issued is an organization, agency or department. This is populated with site-specific assigning authorities. It also should contain national or international codes when CX-5 Identifier Type may be assigned by more than one authority within a governmental or organizational unit. For example, a federal government may have 2 departments that assign a military identifier, its Veterans Affairs department and its department of defense. It is not recommended to include values for entities such as Social Security Administration (SSA), Immigration and Naturalization Service (INS), Center for Medicare and Medicaid Services (CMS) because they are included in the identifier type table. In these cases the name of the country plus the identifier type yields the correct interpretation of the identifier in component one. Likewise, entries like department of motor vehicles (DMV) and licensing boards are not recommended for inclusion because the combination of state and identifier type yields the correct interpretation of the identifier in component one. This approach is not to be confused with the detailed information provided in the chapter 15 segments that have provision for specifying the precise granting body and issuing body information needed in personnel management messages. Example 1: <Identifier> plus <Visa> yields a unique identifier. Example 2: <Identifier> plus <state> plus <DLN> yields a unique driver’s license number. Example 3: <Identifier> plus <country> plus <INS> yields a unique immigration number. The reader is referred to the CX.4, if there is a need to transmit this information as an OID. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Prior Patient Location This component specifies the code for the point where patient care is administered. It is conditional on PL.6 Person Location Type (e.g., nursing unit or department or clinic). After floor, it is the most general patient location designation. Refer to User-defined Table 0302 - Point of care for suggested values. This component specifies the code for the patient's room. After point of care, it is the most general person location designation. Refer to User-defined Table 0303 - Room for suggested values. This component specifies the code for the patient's bed. After room, it is the most general person location designation. Refer to User-defined Table 0304 - Bed for suggested values. This component is subject to site interpretation but generally describes the highest level physical designation of an institution, medical center or enterprise. It is the most general person location designation. (See Section 2.A.33, "HD - hierarchic designator") for discussion of data type. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be redefined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. This component specifies the code for the status or availability of the location. For example, it may convey bed status. Refer to User-defined Table 0306 - Location status for suggested values. Person location type is the categorization of the person’s location defined by facility, building, floor, point of care, room or bed. Although not a required field, when used, it may be the only populated field. It usually includes values such as nursing unit, department, clinic, SNF, physician’s office. Refer to User-defined Table 0305 - Person location type for suggested values. Required if known This component specifies the code for the building where the person is located. After facility, it is the most general person location designation. Refer to User-defined Table 0307 - Building for suggested values. This component specifies the code for the floor where the person is located. After building, it is the most general person location designation. Refer to User-defined Table 0308 - Floor for suggested values. This component describes the location in free text. The unique identifier that represents the physical location as a whole without regard for the individual components. This accommodates sites that may have a different method of defining physical units or who may code at a less granular level. For example, point of care, room, and bed may be 1 indivisible code. The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The entity that creates the data for the individual physical location components. If populated, it should be the authority for all components populated. Refer to User-defined Table 0363 – Assigning authority for suggested values for the first sub-component of the HD component, <namespace ID>. This component makes it possible for codes to be differentiated when the field in which this data type is used repeats. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementors may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Attending Doctor This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Referring Doctor This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Consulting Doctor This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Hospital Service Temporary Location This component specifies the code for the point where patient care is administered. It is conditional on PL.6 Person Location Type (e.g., nursing unit or department or clinic). After floor, it is the most general patient location designation. Refer to User-defined Table 0302 - Point of care for suggested values. This component specifies the code for the patient's room. After point of care, it is the most general person location designation. Refer to User-defined Table 0303 - Room for suggested values. This component specifies the code for the patient's bed. After room, it is the most general person location designation. Refer to User-defined Table 0304 - Bed for suggested values. This component is subject to site interpretation but generally describes the highest level physical designation of an institution, medical center or enterprise. It is the most general person location designation. (See Section 2.A.33, "HD - hierarchic designator") for discussion of data type. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be redefined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. This component specifies the code for the status or availability of the location. For example, it may convey bed status. Refer to User-defined Table 0306 - Location status for suggested values. Person location type is the categorization of the person’s location defined by facility, building, floor, point of care, room or bed. Although not a required field, when used, it may be the only populated field. It usually includes values such as nursing unit, department, clinic, SNF, physician’s office. Refer to User-defined Table 0305 - Person location type for suggested values. Required if known This component specifies the code for the building where the person is located. After facility, it is the most general person location designation. Refer to User-defined Table 0307 - Building for suggested values. This component specifies the code for the floor where the person is located. After building, it is the most general person location designation. Refer to User-defined Table 0308 - Floor for suggested values. This component describes the location in free text. The unique identifier that represents the physical location as a whole without regard for the individual components. This accommodates sites that may have a different method of defining physical units or who may code at a less granular level. For example, point of care, room, and bed may be 1 indivisible code. The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The entity that creates the data for the individual physical location components. If populated, it should be the authority for all components populated. Refer to User-defined Table 0363 – Assigning authority for suggested values for the first sub-component of the HD component, <namespace ID>. This component makes it possible for codes to be differentiated when the field in which this data type is used repeats. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementors may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Preadmit Test Indicator Re-admission Indicator Admit Source Ambulatory Status VIP Indicator Admitting Doctor This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Patient Type Visit Number The value of the identifier itself. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. The algorithm for calculating a Mod10 check digit is as follows: Assume you have an identifier - 12345. Take the odd digit positions, counting from the right, i.e., 531, multiply this number by 2 to get 1062. Take the even digit positions, starting from the right (i.e., 42), prepend these to the 1062 to get 421062. Add all of these six digits together to get 15. Subtract this number from the next highest multiple of 10, i.e., 20 - 15 to get 5. The Mod10 check digit is 5. The Mod10 check digit for 401 is 0; for 9999, it’s 4; for 99999999, it’s 8. The algorithm for calculating a Mod11 check digit is as follows: Terms d = digit of number starting from units digit, followed by 10’s position, followed by 100’s position, etc. w = weight of digit position starting with the units position, followed by 10’s position, followed by 100’s position etc. Values for w = 2, 3, 4, 5, 6, 7, 2, 3, 4, 5, 6, 7, etc. (repeats for each group of 6 digits) c = check digit Calculation (Step 1) m = sum of (d * w) for positions 1, 2, etc. starting with units digit for d = digit value starting with units position to highest order for w = weight value from 2 to 7 for every six positions starting with units digit (Step 2) c1 = m mod 11 (Step 3) if c1 = 0 then reset c1 = 1 (Step 4) = (11 - c1) mod 10 Example: If the number is 1234567, then the mod 11 check digit = 4 The calculations are: M = (7*2)+(6*3)+(5*4)+(4*5)+(3*6)+(2*7)+(1*2) = 14 + 18 + 20 + 20 + 18 + 14 + 2 = 106 c1 = 106 mod 11 = 7 c = (11-c1) mod 10 = 4 mod 10 = 4 Other variants of these check digit algorithms exist and may be used by local bilateral site agreement. Note: The check digit and code identifying check digit scheme are null if ID is alphanumeric. The assigning authority is a unique name of the system (or organization or agency or department) that creates the data. . Refer to User-defined Table 0363 – Assigning authority for suggested values. The reader is referred to the CX.9 and the CX.10 if there is a need to transmit values with semantic meaning for an assigning jurisdiction or assigning department or agency in addition to, or instead of, an assigning authority. However, all 3 components may be valued. If, in so doing, it is discovered that the values in CX.9 and/or CX.10 conflict with CX.4, the user would look to the Message Profile or other implementation agreement for a statement as to which takes precedence. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the patient. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component), may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The first date, if known, on which the identifier is valid and active. The last date, if known, on which the identifier is valid and active. The geo-political body that assigned the identifier in component 1. Refer to HL7 Table 0399 Country Code in section 2.15.9.17 for valid values if the administrative unit under whose jurisdiction the identifier was issued is a country. Refer to User-Defined Table 0347 State/Province for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a state or province. This table is country specific. In the US postal codes may be used. Refer to User-defined Table –0289 County/Parish for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a county or parish. The reader is referred to the CX.4, if there is a need to transmit this information as an OID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. Refer to User-defined Table –0530 Organizations, Agency, Department for suggested values if the administrative unit under whose jurisdiction the identifier was issued is an organization, agency or department. This is populated with site-specific assigning authorities. It also should contain national or international codes when CX-5 Identifier Type may be assigned by more than one authority within a governmental or organizational unit. For example, a federal government may have 2 departments that assign a military identifier, its Veterans Affairs department and its department of defense. It is not recommended to include values for entities such as Social Security Administration (SSA), Immigration and Naturalization Service (INS), Center for Medicare and Medicaid Services (CMS) because they are included in the identifier type table. In these cases the name of the country plus the identifier type yields the correct interpretation of the identifier in component one. Likewise, entries like department of motor vehicles (DMV) and licensing boards are not recommended for inclusion because the combination of state and identifier type yields the correct interpretation of the identifier in component one. This approach is not to be confused with the detailed information provided in the chapter 15 segments that have provision for specifying the precise granting body and issuing body information needed in personnel management messages. Example 1: <Identifier> plus <Visa> yields a unique identifier. Example 2: <Identifier> plus <state> plus <DLN> yields a unique driver’s license number. Example 3: <Identifier> plus <country> plus <INS> yields a unique immigration number. The reader is referred to the CX.4, if there is a need to transmit this information as an OID. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Financial Class This component contains the financial class assigned to a person. User-defined Table 0064 - Financial class is used as the HL7 identifier for the user-defined table of values for this component. This component contains the effective date/time of the person’s assignment to the financial class specified in the first component. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Charge Price Indicator Courtesy Code Credit Rating Contract Code Contract Effective Date Contract Amount Contract Period Interest Code Transfer to Bad Debt Code Transfer to Bad Debt Date Bad Debt Agency Code Bad Debt Transfer Amount Bad Debt Recovery Amount Delete Account Indicator Delete Account Date Discharge Disposition Discharged to Location Specifies the healthcare facility to which the patient was discharged. Refer to User-defined Table 0113 - Discharged to location for suggested values. Specifies the date on which the patient was discharged to a healthcare facility. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Diet Type Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Servicing Facility Bed Status Account Status Pending Location This component specifies the code for the point where patient care is administered. It is conditional on PL.6 Person Location Type (e.g., nursing unit or department or clinic). After floor, it is the most general patient location designation. Refer to User-defined Table 0302 - Point of care for suggested values. This component specifies the code for the patient's room. After point of care, it is the most general person location designation. Refer to User-defined Table 0303 - Room for suggested values. This component specifies the code for the patient's bed. After room, it is the most general person location designation. Refer to User-defined Table 0304 - Bed for suggested values. This component is subject to site interpretation but generally describes the highest level physical designation of an institution, medical center or enterprise. It is the most general person location designation. (See Section 2.A.33, "HD - hierarchic designator") for discussion of data type. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be redefined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. This component specifies the code for the status or availability of the location. For example, it may convey bed status. Refer to User-defined Table 0306 - Location status for suggested values. Person location type is the categorization of the person’s location defined by facility, building, floor, point of care, room or bed. Although not a required field, when used, it may be the only populated field. It usually includes values such as nursing unit, department, clinic, SNF, physician’s office. Refer to User-defined Table 0305 - Person location type for suggested values. Required if known This component specifies the code for the building where the person is located. After facility, it is the most general person location designation. Refer to User-defined Table 0307 - Building for suggested values. This component specifies the code for the floor where the person is located. After building, it is the most general person location designation. Refer to User-defined Table 0308 - Floor for suggested values. This component describes the location in free text. The unique identifier that represents the physical location as a whole without regard for the individual components. This accommodates sites that may have a different method of defining physical units or who may code at a less granular level. For example, point of care, room, and bed may be 1 indivisible code. The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The entity that creates the data for the individual physical location components. If populated, it should be the authority for all components populated. Refer to User-defined Table 0363 – Assigning authority for suggested values for the first sub-component of the HD component, <namespace ID>. This component makes it possible for codes to be differentiated when the field in which this data type is used repeats. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementors may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Prior Temporary Location This component specifies the code for the point where patient care is administered. It is conditional on PL.6 Person Location Type (e.g., nursing unit or department or clinic). After floor, it is the most general patient location designation. Refer to User-defined Table 0302 - Point of care for suggested values. This component specifies the code for the patient's room. After point of care, it is the most general person location designation. Refer to User-defined Table 0303 - Room for suggested values. This component specifies the code for the patient's bed. After room, it is the most general person location designation. Refer to User-defined Table 0304 - Bed for suggested values. This component is subject to site interpretation but generally describes the highest level physical designation of an institution, medical center or enterprise. It is the most general person location designation. (See Section 2.A.33, "HD - hierarchic designator") for discussion of data type. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be redefined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. This component specifies the code for the status or availability of the location. For example, it may convey bed status. Refer to User-defined Table 0306 - Location status for suggested values. Person location type is the categorization of the person’s location defined by facility, building, floor, point of care, room or bed. Although not a required field, when used, it may be the only populated field. It usually includes values such as nursing unit, department, clinic, SNF, physician’s office. Refer to User-defined Table 0305 - Person location type for suggested values. Required if known This component specifies the code for the building where the person is located. After facility, it is the most general person location designation. Refer to User-defined Table 0307 - Building for suggested values. This component specifies the code for the floor where the person is located. After building, it is the most general person location designation. Refer to User-defined Table 0308 - Floor for suggested values. This component describes the location in free text. The unique identifier that represents the physical location as a whole without regard for the individual components. This accommodates sites that may have a different method of defining physical units or who may code at a less granular level. For example, point of care, room, and bed may be 1 indivisible code. The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The entity that creates the data for the individual physical location components. If populated, it should be the authority for all components populated. Refer to User-defined Table 0363 – Assigning authority for suggested values for the first sub-component of the HD component, <namespace ID>. This component makes it possible for codes to be differentiated when the field in which this data type is used repeats. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementors may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Admit Date/Time The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Discharge Date/Time The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Current Patient Balance Total Charges Total Adjustments Total Payments Alternate Visit ID The value of the identifier itself. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. The algorithm for calculating a Mod10 check digit is as follows: Assume you have an identifier - 12345. Take the odd digit positions, counting from the right, i.e., 531, multiply this number by 2 to get 1062. Take the even digit positions, starting from the right (i.e., 42), prepend these to the 1062 to get 421062. Add all of these six digits together to get 15. Subtract this number from the next highest multiple of 10, i.e., 20 - 15 to get 5. The Mod10 check digit is 5. The Mod10 check digit for 401 is 0; for 9999, it’s 4; for 99999999, it’s 8. The algorithm for calculating a Mod11 check digit is as follows: Terms d = digit of number starting from units digit, followed by 10’s position, followed by 100’s position, etc. w = weight of digit position starting with the units position, followed by 10’s position, followed by 100’s position etc. Values for w = 2, 3, 4, 5, 6, 7, 2, 3, 4, 5, 6, 7, etc. (repeats for each group of 6 digits) c = check digit Calculation (Step 1) m = sum of (d * w) for positions 1, 2, etc. starting with units digit for d = digit value starting with units position to highest order for w = weight value from 2 to 7 for every six positions starting with units digit (Step 2) c1 = m mod 11 (Step 3) if c1 = 0 then reset c1 = 1 (Step 4) = (11 - c1) mod 10 Example: If the number is 1234567, then the mod 11 check digit = 4 The calculations are: M = (7*2)+(6*3)+(5*4)+(4*5)+(3*6)+(2*7)+(1*2) = 14 + 18 + 20 + 20 + 18 + 14 + 2 = 106 c1 = 106 mod 11 = 7 c = (11-c1) mod 10 = 4 mod 10 = 4 Other variants of these check digit algorithms exist and may be used by local bilateral site agreement. Note: The check digit and code identifying check digit scheme are null if ID is alphanumeric. The assigning authority is a unique name of the system (or organization or agency or department) that creates the data. . Refer to User-defined Table 0363 – Assigning authority for suggested values. The reader is referred to the CX.9 and the CX.10 if there is a need to transmit values with semantic meaning for an assigning jurisdiction or assigning department or agency in addition to, or instead of, an assigning authority. However, all 3 components may be valued. If, in so doing, it is discovered that the values in CX.9 and/or CX.10 conflict with CX.4, the user would look to the Message Profile or other implementation agreement for a statement as to which takes precedence. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the patient. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component), may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The first date, if known, on which the identifier is valid and active. The last date, if known, on which the identifier is valid and active. The geo-political body that assigned the identifier in component 1. Refer to HL7 Table 0399 Country Code in section 2.15.9.17 for valid values if the administrative unit under whose jurisdiction the identifier was issued is a country. Refer to User-Defined Table 0347 State/Province for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a state or province. This table is country specific. In the US postal codes may be used. Refer to User-defined Table –0289 County/Parish for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a county or parish. The reader is referred to the CX.4, if there is a need to transmit this information as an OID Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. Refer to User-defined Table –0530 Organizations, Agency, Department for suggested values if the administrative unit under whose jurisdiction the identifier was issued is an organization, agency or department. This is populated with site-specific assigning authorities. It also should contain national or international codes when CX-5 Identifier Type may be assigned by more than one authority within a governmental or organizational unit. For example, a federal government may have 2 departments that assign a military identifier, its Veterans Affairs department and its department of defense. It is not recommended to include values for entities such as Social Security Administration (SSA), Immigration and Naturalization Service (INS), Center for Medicare and Medicaid Services (CMS) because they are included in the identifier type table. In these cases the name of the country plus the identifier type yields the correct interpretation of the identifier in component one. Likewise, entries like department of motor vehicles (DMV) and licensing boards are not recommended for inclusion because the combination of state and identifier type yields the correct interpretation of the identifier in component one. This approach is not to be confused with the detailed information provided in the chapter 15 segments that have provision for specifying the precise granting body and issuing body information needed in personnel management messages. Example 1: <Identifier> plus <Visa> yields a unique identifier. Example 2: <Identifier> plus <state> plus <DLN> yields a unique driver’s license number. Example 3: <Identifier> plus <country> plus <INS> yields a unique immigration number. The reader is referred to the CX.4, if there is a need to transmit this information as an OID. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Visit Indicator Other Healthcare Provider This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Prior Pending Location This component specifies the code for the point where patient care is administered. It is conditional on PL.6 Person Location Type (e.g., nursing unit or department or clinic). After floor, it is the most general patient location designation. Refer to User-defined Table 0302 - Point of care for suggested values. This component specifies the code for the patient's room. After point of care, it is the most general person location designation. Refer to User-defined Table 0303 - Room for suggested values. This component specifies the code for the patient's bed. After room, it is the most general person location designation. Refer to User-defined Table 0304 - Bed for suggested values. This component is subject to site interpretation but generally describes the highest level physical designation of an institution, medical center or enterprise. It is the most general person location designation. (See Section 2.A.33, "HD - hierarchic designator") for discussion of data type. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be redefined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. This component specifies the code for the status or availability of the location. For example, it may convey bed status. Refer to User-defined Table 0306 - Location status for suggested values. Person location type is the categorization of the person’s location defined by facility, building, floor, point of care, room or bed. Although not a required field, when used, it may be the only populated field. It usually includes values such as nursing unit, department, clinic, SNF, physician’s office. Refer to User-defined Table 0305 - Person location type for suggested values. Required if known This component specifies the code for the building where the person is located. After facility, it is the most general person location designation. Refer to User-defined Table 0307 - Building for suggested values. This component specifies the code for the floor where the person is located. After building, it is the most general person location designation. Refer to User-defined Table 0308 - Floor for suggested values. This component describes the location in free text. The unique identifier that represents the physical location as a whole without regard for the individual components. This accommodates sites that may have a different method of defining physical units or who may code at a less granular level. For example, point of care, room, and bed may be 1 indivisible code. The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The entity that creates the data for the individual physical location components. If populated, it should be the authority for all components populated. Refer to User-defined Table 0363 – Assigning authority for suggested values for the first sub-component of the HD component, <namespace ID>. This component makes it possible for codes to be differentiated when the field in which this data type is used repeats. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementors may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Accommodation Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Admit Reason Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Transfer Reason Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Patient Valuables Patient Valuables Location Visit User Code Expected Admit Date/Time The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Expected Discharge Date/Time The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Estimated Length of Inpatient Stay Actual Length of Inpatient Stay Visit Description Referral Source Code This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Previous Service Date Employment Illness Related Indicator Purge Status Code Purge Status Date Special Program Code Retention Indicator Expected Number of Insurance Plans Visit Publicity Code Visit Protection Indicator Clinic Organization Name The name of the specified organization. A code that represents the type of name i.e., legal name, display name. Refer to User-defined Table 0204 - Organizational Name Type for suggested values. This component has been retained for backward compatibility only as of v 2.5. It is recommended to use component 10 Organization identifier that accommodates alphanumeric identifiers. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. The check digit scheme codes are defined in HL7 Table 0061 - Check digit scheme. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Assigning authorities are unique across a given HL7 implementation. Refer to User-defined Table 0363 - Assigning Authority for suggested values. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e. even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation code for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component contains the sequence of characters (the code) that uniquely identifies the item being referenced by XON.1 Organization Name. This component replaces XON.3 ID Number as of v 2.5. Note: The check digit and code identifying check digit scheme are null if Organization identifier is alphanumeric. Patient Status Code Visit Priority Code Previous Treatment Date Expected Discharge Disposition Signature on File Date First Similar Illness Date Patient Charge Adjustment Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Recurring Service Code Billing Media Code Expected Surgery Date and Time The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Military Partnership Code Military Non-Availability Code Newborn Baby Indicator Baby Detained Indicator Mode of Arrival Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Recreational Drug Use Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Admission Level of Care Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Precaution Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Patient Condition Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Living Will Code Organ Donor Code Advance Directive Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Patient Status Effective Date Expected LOA Return Date/Time The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Expected Pre-admission Testing Date/Time The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Notify Clergy Code Set ID - AL1 Allergen Type Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Allergen Code/Mnemonic/Description Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Allergy Severity Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Allergy Reaction Code Identification Date - Order Control. Bepaalt de functie van het aanvraagsegment. Zie HL7 Tabel 0119 - Order Control Codes And Their Meaning voor geldige waarden. De initiële status van een aanvraag is altijd "NW". Het ORC-segment kan voorkomen in diverse berichten, waaronder het aanvraagbericht OM^O21 en het aanvraagbevestigingbericht ORL^O22 en uiteindelijk ook het resultaatbericht OUL^R22. Of er gebruik wordt gemaakt van ORL^O22, hangt af van lokale afspraken. Order Control Codes / Trigger Event MatrixCodeOML^O21ORL^O22OUL^R22toelichtingNWYNieuwOKYYOK, order geaccepteerdUAYOrder niet geaccepteerd (unable to accept) De aanvrager kan aanvragen eventueel nog aanvullen, annuleren en stoppen: HL7 Tabel 0119 heeft voor alle gevallen aparte codes. Er wordt binnen Lab2Lab in principe geen gebruik wordt gemaakt van meer complexe processturing dan hierboven afgebeeld, maar hier kunnen lokaal andere afspraken over worden gemaakt.Aanvragen voor RIVM Type-Ned moeten de code NW bevatten en hierop volgt een aanvraagbevestiging met OK of UA per aanvraag. Aanvraagnummer (Placer Order Number) van het uitbestedende laboratorium. Om unieke identificatie te kunnen garanderen, is de verwachting dat deze identificatie begint met het driecijferige labid van het lab dat dit nummer heeft uitgedeeld. The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Aanvraagnummer (Filler Order Number) van het inbestedende laboratorium. Om unieke identificatie te kunnen garanderen, is de verwachting dat deze identificatie begint met het driecijferige labid van het lab dat dit nummer heeft uitgedeeld. Het Aanvraagnummer van het inbestedende laboratorium wordt verwacht bij ieder ORC segment waarvoor een inbestedend laboratorium resultaten produceert The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Aanvraagnummer (Placer Group Number) van het uitbestedende laboratorium. Als uit een aanvraag, een of meerdere andere aanvragen worden gegenereerd, bijvoorbeeld separate isolaatgevoeligheidpanels, dan bevat dit veld de koppeling naar de aanvraag waaruit ORC|2 is voortgekomen. Om unieke identificatie te kunnen garanderen, is de verwachting dat deze identificatie begint met het driecijferige labid van het lab dat dit nummer heeft uitgedeeld. The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Order Status Response Flag Quantity/Timing This component specifies the quantity of the service that should be provided at each service interval. For example, if two blood cultures are to be obtained every 4 hours, the quantity would be 2. If three units of blood are to be typed and cross-matched, the quantity would be 3. The default value is 1. When units are required, they can be added, specified by a subcomponent delimiter. Note: The component contains the complex data type CQ and cannot be fully expressed. CQ cannot be legally expressed when embedded within another data type. This component specifies the numeric quantity or amount of an entity. This component species the units in which the quantity is expressed. Field-by-field, default units may be defined within the specifications. When the quantity is measured in the default units, the units need not be transmitted. If the quantity is recorded in units different from the default, the units must be transmitted. Determines the interval between repeated services. The default is one time only. The repeating frequency with which the treatment is to be administered. It is similar to the frequency and SIG code tables used in order entry systems. Refer to User-defined Table 0335 - Repeat pattern for suggested values. The first component may repeat, with repeat values separated by a space. The repeats are interpreted as connected by logical ANDs. Example: Twice per day, every other day: BID QOD Three times per day, Monday Wednesday and Friday: TID QJ135 Because of this syntax, repeat values should never contain blanks. This component explicitly lists the actual times referenced by the code in the first component, in the following format: HHMM,HHMM,HHMM,.… This second component will be used to clarify the first component in cases where the actual times vary within an institution. If the time of the order spans more than a single day, this new component is only practical if the same times of administration occur for each day of the order. If the actual start time of the order (as given by the fourth component of the quantity/timing field) is after the first explicit time, the first administration is taken to be the first explicit time after the start time. In the case where the patient moves to a location having a different set of explicit times, the existing order may be updated with a new quantity/timing field showing the changed explicit times. This component indicates how long the service should continue after it is started. The default is INDEF (do indefinitely). This component is coded as follows: Value Description Comments S<integer> <integer> seconds M<integer> <integer> minutes H<integer> <integer> hours D<integer> <integer> days W<integer> <integer> weeks L<integer> <integer> months X<integer> <integer> times at interval specified in the order. A request for 2 blood cultures Q2H X3 would imply obtaining 2 blood cultures 3 different times at 2-hour intervals for a total of 6 blood cultures. T<integer> at the interval and amount stated until a total of <integer> "DOSAGE" is accumulated. Units would be assumed to be the same as in the QUANTITY field. INDEF do indefinitely - also the default This component may be specified by the orderer, in which case it indicates the earliest date/time at which the services should be started. In many cases, however, the start date/time will be implied or will be defined by other fields in the order record (e.g., urgency ‑ STAT). In such a case, this field will be empty. The filling service will often record a value in this field after receipt of the order, however, and compute an end time on the basis of the start date/time for the filling service’s internal use. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| When filled in by the requester of the service, this component should contain the latest date/time that the service should be performed. If it has not been performed by the specified time, it should not be performed at all. The requester may not always fill in this value, yet the filling service may fill it in on the basis of the instruction it receives and the actual start time. Regardless of the value of the end date/time, the service should be stopped at the earliest of the date/times specified by either the duration or the end date/time. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| This component describes the urgency of the request. The following values are suggested (the default for Priority is R): Value Description Comments S Stat With highest priority A ASAP Fill after S orders R Routine Default P Preop C Callback T Timing critical A request implying that it is critical to come as close as possible to the requested time, e.g., for a trough antimicrobial level. PRN As needed If using the value "T" (timing critical), the degree of criticality can be specified thus: Format: Value Description Comments TS<integer> timing critical within <integer> seconds TM<integer> timing critical within <integer> minutes TH<integer> timing critical within <integer> hours TD<integer> timing critical within <integer> days TW<integer> timing critical within <integer> weeks TL<integer> timing critical within <integer> months For the sequential orders specification, these values specify the time criticality with which the predecessor order must be followed by the given order. The priority component may repeat; separate repeating values with a space. This is a free text component that describes the conditions under which the drug is to be given. For example, PRN pain, or to keep blood pressure below 110. The presence of text in this field should be taken to mean that human review is needed to determine the how and/or when this drug should be given. This component is a full text version of the instruction (optional). This non‑null component indicates that a second timing specification is to follow using the repeat delimiter. Refer to HL7 table 0472 - TQ Conjunction ID for valid values Usage Note: There are many situations, such as the creation of an order for a group of intravenous (IV) solutions, where the sequence of the individual intravenous solutions (each a service in itself) needs to be specified, e.g., hyperalimentation with multi-vitamins in every third bottle. There are other situations where part of the order’s instructions contains a results condition of some type, such as "PRN pain". There is currently a free text "condition" component of ORC-7-quantity/timing, which allows any condition to be specified. However, to support a fully encoded version of order sequencing, or results condition, we have defined in the following paragraphs a 10th component of ORC-7-quantity/timing. The sequencing conditions supported by this 10th component are based on the completion of a predecessor service. Identifies whether sequence conditions or a repeating cycle of orders is defined. Refer to HL7-defined Table 0524 – Sequence condition for valid values. Contains the first component of the placer order number, entity identifier. Contains the second component of the placer order number, namespace ID. Refer to user-defined table 0363 - Assigning Authority for suggested values. Contains the first component of the filler order number, entity identifier. Contains the second component of the filler order number, namespace ID. Refer to user-defined table 0363 - Assigning Authority for suggested values Defines the relationship between the start/end of the related predecessor or successor order and the current order from ORC-2, 3 or 4. The acceptable condition values have the form commonly used in project planning methodologies in the following format: <one of "SS", "EE", "SE", or "ES"> +/- <time>. The first letter stands for start (S) or end (E) of predecessor order, where the predecessor is defined by the placer or filler order number in subcomponents 1,2 or subcomponents 3,4. The second letter stands for the start (S) or end (E) of the successor order, where the successor order is the order containing this quantity/timing specification. The time specifies the interval between the predecessor and successor starts or ends (see following examples). Where <time> is defined as: Example Description Comment S<integer> do for <integer> seconds M<integer> do for <integer> minutes H<integer> do for <integer> hours D<integer> do for <integer> days W<integer> do for <integer> weeks L<integer> do for <integer> months The maximum number of repeats to be used only on cyclic groups. The total number of repeats is constrained by the end date/time of the last repeat or the end date/time of the parent, whichever is first. Contains the next to the last component of the placer order number, universal ID. Contains the last component of the placer order number. Refer to HL7 table 0301 - Universal ID Type for valid values. Contains the next to the last component of the filler order number, universal ID. Contains the last component of the placer order number. Refer to HL7 table 0301 - Universal ID Type for valid values. This component contains the duration for a single performance of a service, e.g., whirlpool twenty minutes three times per day for three days. It is optional within TQ and does not repeat. Note: The component delimiter in this CQ is demoted to a subcomponent delimiter. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. This component contains the total number of occurrences of a service that should result from this order. It is optional within TQ and does not repeat. If both the end date/time and the total occurrences are valued and the occurrences would extend beyond the end date/time, then the end date/time takes precedence. Otherwise the number of occurrences takes precedence. Dit veld relateert een child aan zijn parent wanneer een parent-child relatie van toepassing is. ORC-8-parent is hetzelfde als OBR-29-parent. Als de parent niet bestaat in ORC, dan moet deze aanwezig zijn in de bijbehorende OBR. Specifies an identifier assigned to an entity by the placer system. For example, the component might be used to convey the following: placer order number of the parent order the specimen identifier as assigned by the placer. A location identifier assigned (or used by) the placer. The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Specifies an identifier assigned to an entity by the filler system. For example, the component might convey the following: filler order number of the parent order the specimen identifier as assigned by the filler. A location identifier assigned (or used by) the filler. The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Date/Time of Transaction The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Entered By This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Verified By This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Ordering Provider This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Enterer's Location This component specifies the code for the point where patient care is administered. It is conditional on PL.6 Person Location Type (e.g., nursing unit or department or clinic). After floor, it is the most general patient location designation. Refer to User-defined Table 0302 - Point of care for suggested values. This component specifies the code for the patient's room. After point of care, it is the most general person location designation. Refer to User-defined Table 0303 - Room for suggested values. This component specifies the code for the patient's bed. After room, it is the most general person location designation. Refer to User-defined Table 0304 - Bed for suggested values. This component is subject to site interpretation but generally describes the highest level physical designation of an institution, medical center or enterprise. It is the most general person location designation. (See Section 2.A.33, "HD - hierarchic designator") for discussion of data type. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be redefined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. This component specifies the code for the status or availability of the location. For example, it may convey bed status. Refer to User-defined Table 0306 - Location status for suggested values. Person location type is the categorization of the person’s location defined by facility, building, floor, point of care, room or bed. Although not a required field, when used, it may be the only populated field. It usually includes values such as nursing unit, department, clinic, SNF, physician’s office. Refer to User-defined Table 0305 - Person location type for suggested values. Required if known This component specifies the code for the building where the person is located. After facility, it is the most general person location designation. Refer to User-defined Table 0307 - Building for suggested values. This component specifies the code for the floor where the person is located. After building, it is the most general person location designation. Refer to User-defined Table 0308 - Floor for suggested values. This component describes the location in free text. The unique identifier that represents the physical location as a whole without regard for the individual components. This accommodates sites that may have a different method of defining physical units or who may code at a less granular level. For example, point of care, room, and bed may be 1 indivisible code. The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator". See Section 2.A.33.1, "Namespace ID (IS)" for definition. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component See Section 2.A.33.2, "Universal ID (ST)" for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The entity that creates the data for the individual physical location components. If populated, it should be the authority for all components populated. Refer to User-defined Table 0363 – Assigning authority for suggested values for the first sub-component of the HD component, <namespace ID>. This component makes it possible for codes to be differentiated when the field in which this data type is used repeats. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementors may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Call Back Phone Number Specifies the telephone number in a predetermined format that includes an optional extension, beeper number and comment. This component has been retained for backward compatibility only as of version 2.3. Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C any text] Note: Because this component has been deprecated a new data type has not been defined to replace the formatted ST. A code that represents a specific use of a telecommunication number. Refer to HL7 Table 0201 - Telecommunication use code for valid values. A code that represents the type of telecommunication equipment. Refer to HL7 Table 0202 - Telecommunication equipment type for valid values. Internationalization note: To make this data type interoperate with CEN’s Telecommunication data attribute group, we allow use of the second component for email addresses. The presence of an email address is specified by the addition of the value NET to the Phone Use Code table, and the type of Internet address is specified with the values Internet and X.400 to the Phone Equipment Type table. When used for an Internet address, the first component of the XTN data type will be null. If the @-sign is being used as a subcomponent delimiter, the HL7 subcomponent escape sequence may be used when encoding an Internet address (see Section Country Code (NM). Country Code Area/City Code Local Number Extension Contains comments with respect to the telephone number. The characters established within a company’s internal telephone system network used as a prefix to the Extension component for internal dialing. Note that the use of Extension Prefix requires that the Extension component be valued and that digits, as well as special characters (e.g., *, #) may be used. The characters established within a company’s internal telephone system used in place of the (external) telephone number to facilitate calling because its length is shorter than that of the telephone number. Note that digits, as well as special characters (e.g., *, #) may be used. An expression of the telephone number as an unparsible string. The phone number was entered as free text and sending system does not know how to parse it. Order Effective Date/Time The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Order Control Code Reason. Kan de reden bij de waarde in ORC|1 bevatten. Dit is vooral relevant bij waarden anders dan NW en OK. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Entering Organization Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Entering Device Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Action By This string refers to the coded ID according to a user-defined table, defined by the 9th component. If the first component is present, either the source table or the assigning authority must be valued. This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, " FN - family name". The atomic element of the person's family name. In most Western usage, this is the person's last name. Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). Note: Subcomponents <own surname prefix>, <own surname>, <surname prefix from partner/spouse> and <surname from partner/spouse> decompose complex Germanic names such as "Irma de Jong-van Beethoven". If these subcomponents are valued, the <surname> subcomponent should still be fully valued for backward compatibility, i.e., ^de Jong-van Beethoven&de&Jong&van&Beethoven^. Also, for clarity, the <last name prefix> has been renamed to <own surname prefix>. The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. First name. Multiple middle names may be included by separating them with spaces. Used to specify a name suffix (e.g., Jr. or III). Used to specify a name prefix (e.g., Dr.). Retained for backward compatibility only as of v 2.5. See Professional Suffix component. Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values. User-defined Table 0297 – CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component. Required if the first component has a value The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 – Assigning authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component, <namespace ID>. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values. See Section 2.A.88.7, "Name Type Code (ID)". The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check digit scheme for valid values. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the <assigning authority> component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types. I.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Retained for backward compatibility only as of v 2.5. Refer to XCN.19 Effective Date and XCN.20 Expiration Date instead. This component cannot be fully expressed and has been identified as v 2.4 erratum. This component contains the start and end date/times that define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. A code that represents the preferred display order of the components of this person name. Refer to HL7 Table 0444 - Name Assembly Order for valid values. The first date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| The last date, if known, on which the address is valid and active. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management. The geo-political body that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. The agency or department that assigned the identifier in component 1. See section, 2.A.14.9, "Assigning Jurisdiction (CWE)" for further detail. Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Advanced Beneficiary Notice Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. See usage note in section introduction. The descriptive or textual name of the alternate identifier. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Refer to HL7 Table 0396 in section 2.17.5 for valid values. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Ordering Facility Name The name of the specified organization. A code that represents the type of name i.e., legal name, display name. Refer to User-defined Table 0204 - Organizational Name Type for suggested values. This component has been retained for backward compatibility only as of v 2.5. It is recommended to use component 10 Organization identifier that accommodates alphanumeric identifiers. The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null. Contains the code identifying the check digit scheme employed. The check digit scheme codes are defined in HL7 Table 0061 - Check digit scheme. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Assigning authorities are unique across a given HL7 implementation. Refer to User-defined Table 0363 - Assigning Authority for suggested values. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to HL7 Table 0203 - Identifier type for suggested values. The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component). If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. The third component governs the interpretation of the second component of the HD. Note: X400, X500, and DNS are not technically universally valid for all time. Names can be de-registered from an existing user and registered to a new user. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e. even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address representation code for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. This component contains the sequence of characters (the code) that uniquely identifies the item being referenced by XON.1 Organization Name. This component replaces XON.3 ID Number as of v 2.5. Note: The check digit and code identifying check digit scheme are null if Organization identifier is alphanumeric. Ordering Facility Address Adres straat - Vanaf versie 2.4 is ‘street address’ een samengesteld datatype, waar in de verschillende onderdelen van het adres in verschillende subcomponenten kunnen worden opgenomen This component specifies the street or mailing address of a person or institution. When referencing an institution, this first component is used to specify the institution name. When used in connection with a person, this component specifies the first line of the address. Street Name Dwelling Number Huisnummertoevoeging Woonplaats Staat of provincie. Meestal niet relevant, maar gebruiken bij plaatsnamen in meerdere provincies zoals Afferden (Gelderland en Limburg) en Bergen (Noord-Holland en Limburg) Postcode, indien een Nederlandse postcode dan zonder spaties dus bijv. 2316XA. Merk op dat de HL7v3 specificatie met een spatie voorschrijft. Er is hier bewust gekozen voor compatibiliteit met de officiële HL7v2.4 NL specificatie. Land Adrestype. Voor het eerste adres moet deze de waarde ‘M’ (mailing) hebben. Andere adressen kunnen ook worden doorgegeven, zoals bijv. huisadres (‘H’), of tijdelijk/verblijfsadres (‘C’). Andere geografische aanduiding. N.v.t. voor Nederlandse adressen County/graafschap code. N.v.t. voor Nederlandse adressen Census tract. N.v.t. voor Nederlandse adressen. Representatiecode adres. N.v.t. voor Nederlandse adressen Adres geldigheidsperiode. Hierin kunnen eventueel de begin- en einddatum worden doorgegeven waarbinnen een adres geldig is. Dit kan bijv. voor tijdelijke adressen relevant zijn. Het is echter gemarkeerd als obsoleet en behouden voor backward compatbility in versie 2.5. Zie in plaats daarvan XAD.13 en XAD.14. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. Geldigheidsdatum. De eerste datum, indien bekend, waarop het adres geldig is/was en actief. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Verloopdatum. De laatste datum, indien bekend, waarop het adres geldig is/was en actief. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Ordering Facility Phone Number Specifies the telephone number in a predetermined format that includes an optional extension, beeper number and comment. This component has been retained for backward compatibility only as of version 2.3. Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C any text] Note: Because this component has been deprecated a new data type has not been defined to replace the formatted ST. A code that represents a specific use of a telecommunication number. Refer to HL7 Table 0201 - Telecommunication use code for valid values. A code that represents the type of telecommunication equipment. Refer to HL7 Table 0202 - Telecommunication equipment type for valid values. Internationalization note: To make this data type interoperate with CEN’s Telecommunication data attribute group, we allow use of the second component for email addresses. The presence of an email address is specified by the addition of the value NET to the Phone Use Code table, and the type of Internet address is specified with the values Internet and X.400 to the Phone Equipment Type table. When used for an Internet address, the first component of the XTN data type will be null. If the @-sign is being used as a subcomponent delimiter, the HL7 subcomponent escape sequence may be used when encoding an Internet address (see Section Country Code (NM). Country Code Area/City Code Local Number Extension Contains comments with respect to the telephone number. The characters established within a company’s internal telephone system network used as a prefix to the Extension component for internal dialing. Note that the use of Extension Prefix requires that the Extension component be valued and that digits, as well as special characters (e.g., *, #) may be used. The characters established within a company’s internal telephone system used in place of the (external) telephone number to facilitate calling because its length is shorter than that of the telephone number. Note that digits, as well as special characters (e.g., *, #) may be used. An expression of the telephone number as an unparsible string. The phone number was entered as free text and sending system does not know how to parse it. Ordering Provider Address Adres straat - Vanaf versie 2.4 is ‘street address’ een samengesteld datatype, waar in de verschillende onderdelen van het adres in verschillende subcomponenten kunnen worden opgenomen This component specifies the street or mailing address of a person or institution. When referencing an institution, this first component is used to specify the institution name. When used in connection with a person, this component specifies the first line of the address. Street Name Dwelling Number Huisnummertoevoeging Woonplaats Staat of provincie. Meestal niet relevant, maar gebruiken bij plaatsnamen in meerdere provincies zoals Afferden (Gelderland en Limburg) en Bergen (Noord-Holland en Limburg) Postcode, indien een Nederlandse postcode dan zonder spaties dus bijv. 2316XA. Merk op dat de HL7v3 specificatie met een spatie voorschrijft. Er is hier bewust gekozen voor compatibiliteit met de officiële HL7v2.4 NL specificatie. Land Adrestype. Voor het eerste adres moet deze de waarde ‘M’ (mailing) hebben. Andere adressen kunnen ook worden doorgegeven, zoals bijv. huisadres (‘H’), of tijdelijk/verblijfsadres (‘C’). Andere geografische aanduiding. N.v.t. voor Nederlandse adressen County/graafschap code. N.v.t. voor Nederlandse adressen Census tract. N.v.t. voor Nederlandse adressen. Representatiecode adres. N.v.t. voor Nederlandse adressen Adres geldigheidsperiode. Hierin kunnen eventueel de begin- en einddatum worden doorgegeven waarbinnen een adres geldig is. Dit kan bijv. voor tijdelijke adressen relevant zijn. Het is echter gemarkeerd als obsoleet en behouden voor backward compatbility in versie 2.5. Zie in plaats daarvan XAD.13 en XAD.14. The first component contains the earliest date/time (time stamp) in the specified range. The second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision. Geldigheidsdatum. De eerste datum, indien bekend, waarop het adres geldig is/was en actief. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Verloopdatum. De laatste datum, indien bekend, waarop het adres geldig is/was en actief. The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Order Status Modifier Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Advanced Beneficiary Notice Override Reason Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Filler's Expected Availability Date/Time The point in time. See section 2.A.22, "DTM - date/time" for the full description of this component Retained only for purposes of backward compatibility as of v 2.3. Refer to component 1 for current method of designating degree of precision. Definition: Indicates the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Refer to HL7 Table 0529 – Precision for valid value. Note that the Degree of Precision is either the same as or overrides the precision indicated by the first component. It may not indicate greater precision. In the following example, the second component overrides the first and indicates a lesser precision, April 1999. |199904011200^L| Confidentiality Code Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned. Order Type Sequence of characters (the code) that uniquely identifies the item being referenced. Different coding schemes will have different elements here. The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Identifies the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier. Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes and other coding systems. Some organizations that publish code sets author more than one. The coding system, then, to be unique is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number. An alternate sequence of characters (the code) that uniquely identifies the item being referenced. Analogous to "Identifier" in component 1. See usage note in section introduction. The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage note in section introduction. Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" above. See usage note in section introduction. This is the version ID for the coding system identified by components 1-3. It belongs conceptually to the group of component 1-3 and appears here only for reasons of backward compatibility. This is the version ID for the coding system identified by components 4-6. It belongs conceptually to the group of alternate components (See usage note in section introduction) and appears here only for reasons of backward compatibility. The original text that was available to an automated process or a human before a specific code was assigned.