Progetto IESS Integrazione per l Erogazione di Servizi in Sanità

Transcription

1 Appendice B: Segmenti HL7 utilizzati INTRODUZIONE I segmenti utilizzati in questo progetto sono una piccola parte di quelli definiti nello standard HL7, essendo la questione della gestione dell'ordine solo uno dei molti argomenti trattati dallo standard. Qui sotto riportiamo una tabella riassuntiva dei singoli segmenti, fornendo come riferimento il Capitolo dello standard in cui vengono trattati. Si ricorda che per semplicità non si sono tradotte letteralmente le definizioni, che quindi vengono riportate in lingua inglese, preferendo aggiungere in lingua italiana un semplice commento. Segmento Nome Capitolo HL7 MSH MSA EVN PID PV1 Segmento di controllo del messaggio Segmento di acknoledgment Segmento di gestione eventi Segmento dati anagrafici Segmento dati anagrafici SEGMENTO DI CONTROLLO DEL MESSAGGIO (MSH) In accordo con lo standard HL7 ogni messaggio deve iniziare con il segmento di controllo (MSH). La tabella seguente descrive il segmento MSH. SEQ LEN DT OPT RP/# TBL# ITEM # ELEMENT NAME 1 1 ST R Field Separator 2 4 ST R Encoding Characters EI R Sending Application EI R Sending Facility EI R Receiving Application EI R Receiving Facility 7 26 TS O Date/Time Of Message 8 40 ST O Security 9 7 CM R Message Type ST R Message Control ID Nome documento: COOPERAZIONE_CUP v.1.0 Pagina 152 di 220

2 SEQ LEN DT OPT RP/# TBL# ITEM # ELEMENT NAME 11 3 PT R Processing ID VID R Version ID NM O Sequence Number ST O Continuation Pointer 15 2 ID O Accept Acknowledgment Type 16 2 ID O Application Acknowledgment Type 17 2 ID O Country Code ID C Y Character Set CE O Principal Language Of Message ID O Alternate Character Set Handling Scheme Nota: si riporteranno in colore giallo i campi obbligatori, in colore azzurro i campi condizionali, in colore verde i campi obbligatori per IHE, in colore rosso i campi ritenuti obbligatori per il progetto descritto in questo documento, e in colore bianco i campi facoltativi. La struttura XML è definita come: <!ENTITY % MSH.CONTENT "(MSH.1,MSH.2,MSH.3?,MSH.4?,MSH.5?,MSH.6?,MSH.7?,MSH.8?,MSH.9,MSH.10,MSH.11,MSH. 12,MSH.13?,MSH.14?,MSH.15?,MSH.16?,MSH.17?,MSH.18.LST?,MSH.19?,MSH.20?)"> <!ELEMENT MSH %MSH.CONTENT;> Per meglio interpretare il contenuto dei vari campi del segmento MSH si riporta una breve descrizione dei campi obbligatori, mentre per gli altri si rimanda al capitolo relativo nella documentazione HL Non si sono tradotte le definizioni inglesi, ma si sono aggiunte delle note esplicative in italiano (carattere blu). Field separator (ST) Definition: This field contains the separator between the segment ID and the first real field, MSH-2- encoding characters. As such it serves as the separator and defines the character to be used as a separator for the rest of the message. Recommended value is, (ASCII 124). Il valore prescelto è La definizione in xml è: <!ENTITY % MSH.1.CONTENT "%ST;"> <!ELEMENT MSH.1 %MSH.1.CONTENT;> <!ENTITY % MSH.1.ATTRIBUTES "Item CDATA #FIXED '1' Table CDATA #FIXED '0' LongName CDATA #FIXED 'Field Separator' Type CDATA #FIXED 'ST'"> <!ATTLIST MSH.1 %MSH.1.ATTRIBUTES;> Nome documento: COOPERAZIONE_CUP v.1.0 Pagina 153 di 220

3 Encoding characters (ST) Definition: This field contains the four characters in the following order: the component separator, repetition separator, escape character, and subcomponent separator. Recommended values are ^~\&, (ASCII 94, 126, 92, and 38, respectively). I valori scelti sono ^~\& La definizione in xml è: <!ENTITY % MSH.2.CONTENT "%ST;"> <!ELEMENT MSH.2 %MSH.2.CONTENT;> <!ENTITY % MSH.2.ATTRIBUTES "Item CDATA #FIXED '2' Table CDATA #FIXED '0' LongName CDATA #FIXED 'Encoding Characters' Type CDATA #FIXED 'ST'"> <!ATTLIST MSH.2 %MSH.2.ATTRIBUTES;> Sending application (EI) Components: <namespace ID (IS)> ^ <universal ID (ST)> ^ <universal ID type (ID)> Definition: This field uniquely identifies the sending application among all other applications within the network enterprise. The network enterprise consists of all those applications that participate in the exchange of HL7 messages within the enterprise. Entirely site-defined. Il valore di questo campo sarà l'identificativo della Struttura Sanitaria che inizia la transizione, definito in una apposita tabella. La struttura XML è: <!ENTITY % MSH.3.CONTENT "%HD;"> <!ELEMENT MSH.3 %MSH.3.CONTENT;> <!ENTITY % MSH.3.ATTRIBUTES "Item CDATA #FIXED '3' Table CDATA #FIXED '361' LongName CDATA #FIXED 'Sending Application' Type CDATA #FIXED 'HD'"> <!ATTLIST MSH.3 %MSH.3.ATTRIBUTES;> Sending facility (EI) Components: <namespace ID (IS)> ^ <universal ID (ST)> ^ <universal ID type (ID)> Definition: This field contains the address of one of several occurrences of the same application within the sending system. Absent other considerations, the Medicare Provider ID might be used with an appropriate sub-identifier in the second component. Entirely user-defined. Il valore di questo campo sarà l'identificativo della procedura della Struttura Sanitaria che inizia la transizione, definito in una apposita tabella. La struttura XML è: <!ENTITY % MSH.4.CONTENT "%HD;"> <!ELEMENT MSH.4 %MSH.4.CONTENT;> <!ENTITY % MSH.4.ATTRIBUTES "Item CDATA #FIXED '4' Table CDATA #FIXED '362' LongName CDATA #FIXED 'Sending Facility' Type CDATA #FIXED 'HD'"> <!ATTLIST MSH.4 %MSH.4.ATTRIBUTES;> Nome documento: COOPERAZIONE_CUP v.1.0 Pagina 154 di 220

4 Receiving application (EI) Components: <namespace ID (IS)> ^ <universal ID (ST)> ^ <universal ID type (ID)> Definition: This field uniquely identifies the receiving application among all other applications within the network enterprise. The network enterprise consists of all those applications that participate in the exchange of HL7 messages within the enterprise. Entirely site-defined. Il valore di questo campo sarà l'identificativo della Struttura Sanitaria che risponde alla transizione, definito in una apposita tabella. La struttura XML è: <!ENTITY % MSH.5.CONTENT "%HD;"> <!ELEMENT MSH.5 %MSH.5.CONTENT;> <!ENTITY % MSH.5.ATTRIBUTES "Item CDATA #FIXED '5' Table CDATA #FIXED '361' LongName CDATA #FIXED 'Receiving Application' Type CDATA #FIXED 'HD'"> <!ATTLIST MSH.5 %MSH.5.ATTRIBUTES;> Receiving facility (EI) Components: <namespace ID (IS)> ^ <universal ID (ST)> ^ <universal ID type (ID)> Definition: This field identifies the receiving application among multiple identical instances of the application running on behalf of different organizations. See comments: MSH-4-sending facility. Entirely site-defined. Il valore di questo campo sarà l'identificativo della procedura della Struttura Sanitaria che risponde alla transizione, definito in una apposita tabella. La struttura XML è: <!ENTITY % MSH.6.CONTENT "%HD;"> <!ELEMENT MSH.6 %MSH.6.CONTENT;> <!ENTITY % MSH.6.ATTRIBUTES "Item CDATA #FIXED '6' Table CDATA #FIXED '362' LongName CDATA #FIXED 'Receiving Facility' Type CDATA #FIXED 'HD'"> <!ATTLIST MSH.6 %MSH.6.ATTRIBUTES;> Message type (CM) Components: <message type (ID)> ^ <trigger event (ID)> ^ <message structure (ID)> Definition: This field contains the message type, trigger event, and abstract message structure code for the message. The first component is the message type edited by HL7 table Message type; second is the trigger event code edited by HL7 table Event type; third is the abstract message structure code edited by HL7 Table Message structure. The receiving system uses this field to recognize the data segments, and possibly, the application to which to route this message. For certain queries, which may have more than a single response event type, the second component may, in the response message, vary to indicate the response event type. See the discussion of the display query variants in the Standard Section The second component is not required on response or acknowledgment messages. La struttura XML è: <!ENTITY % MSH.9.CONTENT "%CM_MSG_TYPE;"> Nome documento: COOPERAZIONE_CUP v.1.0 Pagina 155 di 220

5 <!ELEMENT MSH.9 %MSH.9.CONTENT;> <!ENTITY % MSH.9.ATTRIBUTES "Item CDATA #FIXED '9' Table CDATA #FIXED '76' LongName CDATA #FIXED 'Message Type' Type CDATA #FIXED 'CM_MSG_TYPE'"> <!ATTLIST MSH.9 %MSH.9.ATTRIBUTES;> Message control ID (ST) Definition: This field contains a number or other identifier that uniquely identifies the message. The receiving system echoes this ID back to the sending system in the Message acknowledgment segment (MSA). La struttura XML è: <!ENTITY % MSH.10.CONTENT "%ST;"> <!ELEMENT MSH.10 %MSH.10.CONTENT;> <!ENTITY % MSH.10.ATTRIBUTES "Item CDATA #FIXED '10' Table CDATA #FIXED '0' LongName CDATA #FIXED 'Message Control ID' Type CDATA #FIXED 'ST'"> <!ATTLIST MSH.10 %MSH.10.ATTRIBUTES;> Processing ID (PT) Components: <processing ID (ID)> ^ <processing mode (ID)> Definition: This field is used to decide whether to process the message as defined in HL7 Application (level 7) Processing rules, above. The first component defines whether the message is part of a production, training, or debugging system (refer to HL7 table Processing ID for valid values). Il valore di default scelto è P. The second component defines whether the message is part of an archival process or an initial load (refer to HL7 table Processing mode for valid values). This allows different priorities to be given to different processing modes. Il valore di default prescelto è not present (null) Table Processing ID Value D P T Description Debugging Production Training Table Processing mode Value A R I not present Description Archive Restore from archive Initial load Not present (the default, meaning current processing) Nome documento: COOPERAZIONE_CUP v.1.0 Pagina 156 di 220

6 Version ID (VID) Components: <version ID (ID)> ^ <internationalization code (CE)> ^ <internal version ID (CE)> Definition: This field is matched by the receiving system to its own version to be sure the message will be interpreted correctly. In version 2.3.1, it has two additional internationalization components, for use by HL7 international affiliates. The Internationalization code is CE data type (using the ISO country codes where appropriate) which represents the HL7 affiliate. The Internal version ID is used if the HL7 Affiliate has more than a single local version associated with a single US version. The Internal version ID has a CE data type, since the table values vary for each HL7 Affiliate. Nel caso specifico del progetto descritto in questo documento l'unico valore possibile per questo campo è 2.3.1, senza alcuna altra specifica per i due sottocampi internationalization code e internal version ID La struttura XML è: <!ENTITY % MSH.12.CONTENT "%VID;"> <!ELEMENT MSH.12 %MSH.12.CONTENT;> <!ENTITY % MSH.12.ATTRIBUTES "Item CDATA #FIXED '12' Table CDATA #FIXED '104' LongName CDATA #FIXED 'Version ID' Type CDATA #FIXED 'VID'"> <!ATTLIST MSH.12 %MSH.12.ATTRIBUTES;> Character set (ID) Definition: This field contains the character set for the entire message. Refer to HL7 table Alternate character sets for valid values. Il valore di default per il progetto descritto in questo documento è 8859/2 Note: The field separator character must still be chosen from the printable 7-bit ASCII character set. The repetitions of this field to specify different character sets apply only to fields of the PN and XPN data types. The field MSH-18-character set is an optional, repeating field of data type ID, using IDs outlined in HL7 table Alternate character sets (or equivalents from ISO 2375). if the field is not valued, the default single-byte character set (ASCII (ISO IR-6)) should be assumed. No other character sets are allowed in the message. if the field repeats, but the first element is NULL (i.e., present but unvalued), the single-byte ASCII (ISO IR-6) is assumed as the default character set. if the sequence is present and the first element is specified, this character set is regarded as the default character set for the message. This must be a single-byte character set (i.e., ISO-IR 6, ISO-IR 13, ISO-IR 14, ISO-IR 100, etc.). elements in the remainder of the sequence (i.e., elements 2..n) are alternate character sets that may be used. These may include multi-byte character sets (i.e., JIS X 0208). the default character set should always be a single-byte character set. It should always have ISO-IR 6 (ISO 646) or ISO-IR 14 (JIS X ) in the G0 area. La struttura XML è: <!ENTITY % MSH.18.CONTENT "%ID;"> <!ELEMENT MSH.18 %MSH.18.CONTENT;> <!ENTITY % MSH.18.ATTRIBUTES "Item CDATA #FIXED '692' Nome documento: COOPERAZIONE_CUP v.1.0 Pagina 157 di 220

7 Table CDATA #FIXED '211' LongName CDATA #FIXED 'Character Set' Type CDATA #FIXED 'ID'"> <!ATTLIST MSH.18 %MSH.18.ATTRIBUTES;> Esempio di XML del segmento MSH <MSH> <MSH.1> </MSH.1> <MSH.2>^~\&</MSH.2> <MSH.3><HD.1>LAB</HD.1></MSH.3> <MSH.4><HD.1>767543</HD.1></MSH.4> <MSH.5><HD.1>ADT</HD.1></MSH.5> <MSH.6><HD.1>767543</HD.1></MSH.6> <MSH.7> </MSH.7> <MSH.9> <CM_MSG_TYPE.1>ADT</CM_MSG_TYPE.1> <CM_MSG_TYPE.2>A04</CM_MSG_TYPE.2> </MSH.9> <MSH.10>XX3657</MSH.10> <MSH.11><PT.1>P</PT.1></MSH.11> <MSH.12><VID.1>2.3.1</VID.1></MSH.12> </MSH> SEGMENTO DI ACKNOWLEDGEMENT DEL MESSAGGIO (MSA) In accordo con lo standard HL7 ogni messaggio di acknowledgement deve contenere il segmento MSA. La tabella seguente lo descrive il segmento. MSA attributes SEQ LEN DT OPT RP/# TBL# ITEM # ELEMENT NAME 1 2 ID R Acknowledgment Code 2 20 ST R Message Control ID 3 80 ST O Text Message 4 15 NM O Expected Sequence Number 5 1 ID O Delayed Acknowledgment Type CE O Error Condition La struttura XML è definita come: <!ENTITY % MSA.CONTENT "(MSA.1,MSA.2,MSA.3?,MSA.4?,MSA.5?,MSA.6?)"> <!ELEMENT MSA %MSA.CONTENT;> Nome documento: COOPERAZIONE_CUP v.1.0 Pagina 158 di 220

8 Acknowledgment code (ID) Definition: This field contains an acknowledgment code, see message processing rules. Refer to HL7 table Acknowledgment code for valid values. Si sottolinea che il modo di acknowledgment scelto per il progetto descritto in questo documento è esclusivamente Original Mode. Value Table Acknowledgment code Description AA AE AR CA CE CR Original mode: Application Accept Enhanced mode: Application acknowledgment: Accept Original mode: Application Error Enhanced mode: Application acknowledgment: Error Original mode: Application Reject Enhanced mode: Application acknowledgment: Reject Enhanced mode: Accept acknowledgment: Commit Accept Enhanced mode: Accept acknowledgment: Commit Error Enhanced mode: Accept acknowledgment: Commit Reject La struttura XML è: <!ENTITY % MSA.1.CONTENT "%ID;"> <!ELEMENT MSA.1 %MSA.1.CONTENT;> <!ENTITY % MSA.1.ATTRIBUTES "Item CDATA #FIXED '18' Table CDATA #FIXED '8' LongName CDATA #FIXED 'Acknowledgment Code' Type CDATA #FIXED 'ID'"> <!ATTLIST MSA.1 %MSA.1.ATTRIBUTES;> Message control ID (ST) Definition: This field contains the message control ID of the message sent by the sending system. It allows the sending system to associate this response with the message for which it is intended. La struttura XML è: <!ENTITY % MSA.2.CONTENT "%ST;"> <!ELEMENT MSA.2 %MSA.2.CONTENT;> <!ENTITY % MSA.2.ATTRIBUTES "Item CDATA #FIXED '10' Table CDATA #FIXED '0' LongName CDATA #FIXED 'Message Control ID' Type CDATA #FIXED 'ST'"> <!ATTLIST MSA.2 %MSA.2.ATTRIBUTES;> Esempio di XML del segmento MSA <MSA> Nome documento: COOPERAZIONE_CUP v.1.0 Pagina 159 di 220

9 </MSA> <MSA.1>AA</MSA.1> <MSA.2>ZZ9380</MSA.2> SEGMENTO EVN Questo segmento è utilizzato per comunicare all'applicazione ricevente particolari eventi trigger. La struttura è la seguente: EVN attribute SEQ LEN DT OPT RP/# TBL# ITEM# ELEMENT NAME 1 3 ID O Event Type Code 2 26 TS R Recorded Date/Time 3 26 TS O Date/Time Planned Event 4 3 IS O Event Reason Code 5 60 XCN O Y Operator ID 6 26 TS R Event Occurred La struttura XML è la seguente: <!ENTITY % EVN.CONTENT "(EVN.1?,EVN.2,EVN.3?,EVN.4?,EVN.5.LST?,EVN.6?)"> <!ELEMENT EVN %EVN.CONTENT;> Recorded date/time (TS) Definition: Most systems will default to the system date/time when the transaction was entered, but they should also permit an override. La struttura XML è: <!ENTITY % EVN.2.CONTENT "%TS;"> <!ELEMENT EVN.2 %EVN.2.CONTENT;> <!ENTITY % EVN.2.ATTRIBUTES "Item CDATA #FIXED '100' Table CDATA #FIXED '0' LongName CDATA #FIXED 'Recorded Date/Time' Type CDATA #FIXED 'TS'"> <!ATTLIST EVN.2 %EVN.2.ATTRIBUTES;> Event occurred (TS) Definition: This field contains the date/time that the event actually occurred. For example, on a transfer (A02 (transfer a patient)), this field would contain the date/time the patient was actually transferred. On a cancellation event, this field should contain the date/time that the event being canceled occurred. La struttura XML è: <!ENTITY % EVN.6.CONTENT "%TS;"> Nome documento: COOPERAZIONE_CUP v.1.0 Pagina 160 di 220

10 <!ELEMENT EVN.6 %EVN.6.CONTENT;> <!ENTITY % EVN.6.ATTRIBUTES "Item CDATA #FIXED '1278' Table CDATA #FIXED '0' LongName CDATA #FIXED 'Event Occurred' Type CDATA #FIXED 'TS'"> <!ATTLIST EVN.6 %EVN.6.ATTRIBUTES;> Esempio di XML del segmento EVN <EVN> <EVN.1>A01</EVN.1> <EVN.2> </EVN.2> <EVN.3> </EVN.3> <EVN.4>I</EVN.4> <EVN.6> </EVN.6> </EVN> PID - PATIENT IDENTIFICATION SEGMENT Il segmento PID è utilizzato da tutte le applicazioni come primo scambio dei dati identificativi del paziente, in quanto contiene informazioni sull'identificativo del paziente e i dati anagrafici che, per la maggior parte, non vengono modificati di frequente. Sotto è riportata la tabella che descrive i campi costituenti questo segmento. PID attributes SEQ LEN DT OPT RP/# TBL# ITEM# ELEMENT NAME 1 4 SI O Set ID PID 2 20 CX O Patient ID 3 20 CX R Y Patient Identifier List 4 20 CX O Y Alternate Patient ID - PID 5 48 XPN R Y Patient Name 6 48 XPN O Y Mother s Maiden Name 7 26 TS R Date/Time of Birth 8 1 IS R Sex 9 48 XPN O Y Patient Alias CE O Y Race XAD R2 Y Patient Address 12 4 IS O County Code XTN P Y Phone Number - Home XTN O Y Phone Number - Business CE O Primary Language Nome documento: COOPERAZIONE_CUP v.1.0 Pagina 161 di 220

11 SEQ LEN DT OPT RP/# TBL# ITEM# ELEMENT NAME CE O Marital Status CE O Religion CX R Patient Account Number ST O SSN Number - Patient DLN O Driver's License Number - Patient CX O Y Mother's Identifier CE O Y Ethnic Group ST P Birth Place 24 1 ID O Multiple Birth Indicator 25 2 NM O Birth Order CE O Y Citizenship CE O Veterans Military Status CE O Nationality TS O Patient Death Date and Time 30 1 ID O Patient Death Indicator La struttura XML del segmento è: <!ENTITY % PID.CONTENT "(PID.1?,PID.2?,PID.3.LST,PID.4.LST?,PID.5.LST,PID.6.LST?,PID.7?,PID.8?,PID.9.LST?,PID.10.LST?,PID.11.LST?,PID.12?,PID.13.LST?,PID.14.LST?,PID.15?,PID.16?,PID.17?,PID.18?,PID.19?,PID.20?,PID.21.LST?,PID.22.LST?,PID.23?,PI D.24?,PID.25?,PID.26.LST?,PID.27?,PID.28?,PID.29?,PID.30?)"> <!ELEMENT PID %PID.CONTENT;> Patient identifier list (CX) Components: <ID (ST)> ^ <check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <assigning authority (HD)> ^ <identifier type code (IS)> ^ <assigning facility (HD)> Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)> Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)> Definition: This field contains the list of identifiers (one or more) used by the facility to uniquely identify a patient (e.g., medical record number, billing number, birth registry, national unique individual identifier, etc.). Refer to HL7 table Check digit scheme for valid values. With HL7 v2.3.1, the arbitrary term of internal ID has been removed from the name of this field for clarity. Example: ^4^M11^ADT01^MR^University Hospital Nome documento: COOPERAZIONE_CUP v.1.0 Pagina 162 di 220

12 La struttura XML è: <!ENTITY % PID.3.CONTENT "%CX;"> <!ELEMENT PID.3 %PID.3.CONTENT;> <!ENTITY % PID.3.ATTRIBUTES "Item CDATA #FIXED '106' Table CDATA #FIXED '0' LongName CDATA #FIXED 'Patient Identifier List' Type CDATA #FIXED 'CX'"> <!ATTLIST PID.3 %PID.3.ATTRIBUTES;> In questo campo viene mappato l'identificativo del paziente, che può essere il Codice Sanitario Regionale (CS) o il Codice Fiscale (CF). Preferibilmente si utilizzi il Codice Fiscale (solo nei casi??????????) Riportiamo un esempio del possibile valore: <PID.3.LST> <PID.3> <CX.1> </CX.1> <CX.2>4</CX.2> <CX.3>M11</CX.3> <CX.4>Distretto Villorba</CX.4> <CX.5>CS</CX.5> <CX.6>ULSS n.9</cx.6> </PID.3> </PID.3.LST> Le informazioni obbligatorie sono quelle contenute nei tag <CX.1> e <CX.5> Patient name (XPN) Components: <family name (IS)> & <last name prefix (IS)> ^ <given name (IS)> ^ <middle initial or name (IS)> ^ <suffix (e.g., JR or III) (IS)> ^ <prefix (e.g., DR) (IS)> ^ <degree (e.g., MD) (IS)> ^ <name type code (ID) > ^ <name representation code (ID)> Definition: This field contains the legal name of the patient. All other names for the patient should be sent in PID-9-patient alias. Therefore, the name type code in this field should be L - Legal. Refer to HL7 table Name type for valid values. Repetition of this field is allowed for representing the same name in different character sets. Please refer to the PN data type. Example: Smith^John^J^III^DR^PHD^L Per la descrizione dettagliata di questo campo si consultino le note apposte al datatype XPN. La struttura XML è: <!ENTITY % PID.5.CONTENT "%XPN;"> <!ELEMENT PID.5 %PID.5.CONTENT;> <!ENTITY % PID.5.ATTRIBUTES "Item CDATA #FIXED '108' Table CDATA #FIXED '0' LongName CDATA #FIXED 'Patient Name' Type CDATA #FIXED 'XPN'"> <!ATTLIST PID.5 %PID.5.ATTRIBUTES;> Nome documento: COOPERAZIONE_CUP v.1.0 Pagina 163 di 220

13 Si riporta un esempio: <PID.5.LST> <PID.5> <XPN.1>VOLTOLINA "BALON"</XPN.1> <XPN.2>GIUSEPPINA MARIA</XPN.2> <XPN.7>M</XPN.7> </PID.5> </PID.5.LST> Date/time of birth (TS) Definition: This field contains the patient sdate and time of birth. La struttura XML è: <!ENTITY % PID.7.CONTENT "%TS;"> <!ELEMENT PID.7 %PID.7.CONTENT;> <!ENTITY % PID.7.ATTRIBUTES "Item CDATA #FIXED '110' Table CDATA #FIXED '0' LongName CDATA #FIXED 'Date/Time Of Birth' Type CDATA #FIXED 'TS'"> <!ATTLIST PID.7 %PID.7.ATTRIBUTES;> Si riporta un esempio: <PID.7> </PID.7> Sex (IS) Definition: This field contains the patient s sex. Refer to user-defined table Sex for suggested values. User-defined Table Sex Value Description La struttura XML è: F M O U Femmina Maschio Altro Ignoto <!ENTITY % PID.8.CONTENT "%IS;"> <!ELEMENT PID.8 %PID.8.CONTENT;> <!ENTITY % PID.8.ATTRIBUTES "Item CDATA #FIXED '111' Table CDATA #FIXED '1' LongName CDATA #FIXED 'Sex' Type CDATA #FIXED 'IS'"> <!ATTLIST PID.8 %PID.8.ATTRIBUTES;> Nome documento: COOPERAZIONE_CUP v.1.0 Pagina 164 di 220

14 Patient address (XAD) Components: <street address (ST)> ^ <other designation (ST)> ^ <city (ST)> ^ <state or province (ST)> ^ <zip or postal code(st)> ^ <country (ID)> ^ < address type (ID)> ^ <other geographic designation (ST)> ^ <county/parish code (IS)> ^ <census tract (IS)> ^ <address representation code (ID)> Definition: This field contains the mailing address of the patient. Address type codes are defined by HL7; see HL7 table Address type. Multiple addresses for the same person may be sent in the following sequence: The primary mailing address must be sent first in the sequence (for backward compatibility); if the mailing address is not sent, then a repeat delimiter must be sent in the first sequence. Si consulti il datatype XAD per una descrizione approfondita di tutti i componenti di questo campo. La struttura XML è: <!ENTITY % PID.11.CONTENT "%XAD;"> <!ELEMENT PID.11 %PID.11.CONTENT;> <!ENTITY % PID.11.ATTRIBUTES "Item CDATA #FIXED '114' Table CDATA #FIXED '0' LongName CDATA #FIXED 'Patient Address' Type CDATA #FIXED 'XAD'"> <!ATTLIST PID.11 %PID.11.ATTRIBUTES;> Si riporta un esempio <PID.11.LST> <PID.11> <XAD.1>Via San Liberale 14</XAD.1> <XAD.3>Padova</XAD.3> <XAD.4>PD</XAD.4> <XAD.5>35128</XAD.5> </PID.11> </PID.11.LST> Phone number - home (XTN) Components: [NNN] [(999)] [X99999] [B99999] [C any text] ^ <telecommunication use code (ID)> ^ <telecommunication equipment type (ID)> ^ < address (ST)> ^ <country code (NM)> ^ <area/city code (NM)> ^ <phone number (NM)> ^ <extension (NM)> ^ <any text (ST)> Definition: This field contains the patient s personal phone numbers. All personal phone numbers for the patient are sent in the following sequence. The first sequence is considered the primary number (for backward compatibility). If the primary number is not sent, then a repeat delimiter is sent in the first sequence. Refer to HL7 tables Telecommunication use code and Telecommunication equipment type for valid values. La struttura XML è: <!ENTITY % PID.13.CONTENT "%XTN;"> <!ELEMENT PID.13 %PID.13.CONTENT;> <!ENTITY % PID.13.ATTRIBUTES "Item CDATA #FIXED '116' Table CDATA #FIXED '0' LongName CDATA #FIXED 'Phone Number - Home' Type CDATA #FIXED 'XTN'"> <!ATTLIST PID.13 %PID.13.ATTRIBUTES;> Nome documento: COOPERAZIONE_CUP v.1.0 Pagina 165 di 220

15 Patient account number (CX) Components: <ID (ST)> ^ <check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <assigning authority (HD)> ^ <identifier type code (IS)> ^ <assigning facility (HD)> Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)> Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)> Definition: This field contains the patient account number assigned by accounting to which all charges, payments, etc., are recorded. It is used to identify the patient s account. Refer to HL7 table Check digit scheme in Chapter 2. Si utilizzi questo campo per riportare il Codice Fiscale del paziente. La struttura XML è: <!ENTITY % PID.18.CONTENT "%CX;"> <!ELEMENT PID.18 %PID.18.CONTENT;> <!ENTITY % PID.18.ATTRIBUTES "Item CDATA #FIXED '121' Table CDATA #FIXED '0' LongName CDATA #FIXED 'Patient Account Number' Type CDATA #FIXED 'CX'"> <!ATTLIST PID.18 %PID.18.ATTRIBUTES;> Esempio di XML del segmento PID <PID> <PID.1>1</PID.1> <PID.3> <CX.1> </CX.1> <CX.2>4</CX.2> <CX.3>M11</CX.3> <CX.4>Distretto Villorba</CX.4> <CX.5>CS</CX.5> <CX.6>ULSS n.9</cx.6> </PID.3> <PID.5.LST> <PID.5> <XPN.1>VOLTOLINA "BALIN"</XPN.1> <XPN.2>MARIA ANTONIETTA</XPN.2> <XPN.3>M</XPN.3> </PID.5> </PID.5.LST> <PID.7> </PID.7> <PID.8>F</PID.8> <PID.11.LST> <PID.11> <XAD.1>VIA SAN LIBERALE 14</XAD.1> <XAD.3>PADOVA</XAD.3> <XAD.4>PD</XAD.4> <XAD.5>35128</XAD.5> </PID.11> Nome documento: COOPERAZIONE_CUP v.1.0 Pagina 166 di 220

16 </PID.11.LST> <PID.13.LST> <PID.13><XTN.1> </XTN.1></PID.13> </PID.13.LST> <PID.18><CX.1>VLTMRR59E60V567Q</CX.1></PID.18> </PID> PV1 - PATIENT VISIT SEGMENT Questo segmento contiene le informazioni sul paziente relativamente ad una specifica richiesta di prestazioni. La sua Struttura è la seguente: SEQ LEN DT OPT RP/# TBL# ITEM# ELEMENT NAME 1 4 SI O Set ID - PV1 2 1 IS R Patient Class 3 80 PL C Assigned Patient Location 4 2 IS O Admission Type 5 20 CX O Preadmit Number 6 80 PL O Prior Patient Location 7 60 XCN C Y Attending Doctor 8 60 XCN C Y Referring Doctor 9 60 XCN R2 Y Consulting Doctor 10 3 IS C Hospital Service PL O Temporary Location 12 2 IS O Preadmit Test Indicator 13 2 IS O Re-admission Indicator 14 3 IS O Admit Source 15 2 IS C Y Ambulatory Status 16 2 IS O VIP Indicator XCN C Y Admitting Doctor 18 2 IS O Patient Type CX C Visit Number FC O Y Financial Class 21 2 IS O Charge Price Indicator Nome documento: COOPERAZIONE_CUP v.1.0 Pagina 167 di 220

17 SEQ LEN DT OPT RP/# TBL# ITEM# ELEMENT NAME 22 2 IS O Courtesy Code 23 2 IS O Credit Rating 24 2 IS O Y Contract Code 25 8 DT O Y Contract Effective Date NM O Y Contract Amount 27 3 NM O Y Contract Period 28 2 IS O Interest Code 29 1 IS O Transfer to Bad Debt Code 30 8 DT O Transfer to Bad Debt Date IS O Bad Debt Agency Code NM O Bad Debt Transfer Amount NM O Bad Debt Recovery Amount 34 1 IS O Delete Account Indicator 35 8 DT O Delete Account Date 36 3 IS O Discharge Disposition CM O Discharged to Location CE O Diet Type 39 2 IS O Servicing Facility 40 1 IS B Bed Status 41 2 IS O Account Status PL O Pending Location PL O Prior Temporary Location TS O Admit Date/Time TS O Discharge Date/Time NM O Current Patient Balance NM O Total Charges NM O Total Adjustments NM O Total Payments CX O Alternate Visit ID Nome documento: COOPERAZIONE_CUP v.1.0 Pagina 168 di 220

18 SEQ LEN DT OPT RP/# TBL# ITEM# ELEMENT NAME 51 1 IS C Visit Indicator XCN O Y Other Healthcare Provider La struttura XML del segmento PV1 è la seguente: <!ENTITY % PV1.7.LST.CONTENT "(PV1.7)+"> <!ELEMENT PV1.7.LST %PV1.7.LST.CONTENT;> <!ENTITY % PV1.8.LST.CONTENT "(PV1.8)+"> <!ELEMENT PV1.8.LST %PV1.8.LST.CONTENT;> <!ENTITY % PV1.9.LST.CONTENT "(PV1.9)+"> <!ELEMENT PV1.9.LST %PV1.9.LST.CONTENT;> <!ENTITY % PV1.15.LST.CONTENT "(PV1.15)+"> <!ELEMENT PV1.15.LST %PV1.15.LST.CONTENT;> <!ENTITY % PV1.17.LST.CONTENT "(PV1.17)+"> <!ELEMENT PV1.17.LST %PV1.17.LST.CONTENT;> <!ENTITY % PV1.20.LST.CONTENT "(PV1.20)+"> <!ELEMENT PV1.20.LST %PV1.20.LST.CONTENT;> <!ENTITY % PV1.24.LST.CONTENT "(PV1.24)+"> <!ELEMENT PV1.24.LST %PV1.24.LST.CONTENT;> <!ENTITY % PV1.25.LST.CONTENT "(PV1.25)+"> <!ELEMENT PV1.25.LST %PV1.25.LST.CONTENT;> <!ENTITY % PV1.26.LST.CONTENT "(PV1.26)+"> <!ELEMENT PV1.26.LST %PV1.26.LST.CONTENT;> <!ENTITY % PV1.27.LST.CONTENT "(PV1.27)+"> <!ELEMENT PV1.27.LST %PV1.27.LST.CONTENT;> <!ENTITY % PV1.52.LST.CONTENT "(PV1.52)+"> <!ELEMENT PV1.52.LST %PV1.52.LST.CONTENT;> <!ENTITY % PV1.CONTENT "(PV1.1?,PV1.2,PV1.3?,PV1.4?,PV1.5?,PV1.6?,PV1.7.LST?,PV1.8.LST?,PV1.9.LST?,PV1.10?,PV1.11?,PV1.12?,PV1.13?, PV1.14?,PV1.15.LST?,PV1.16?,PV1.17.LST?,PV1.18?,PV1.19?,PV1.20.LST?,PV1.21?,PV1.22?,PV1.23?,PV1.24.LST?,P V1.25.LST?,PV1.26.LST?,PV1.27.LST?,PV1.28?,PV1.29?,PV1.30?,PV1.31?,PV1.32?,PV1.33?,PV1.34?,PV1.35?,PV1.36?, PV1.37?,PV1.38?,PV1.39?,PV1.40?,PV1.41?,PV1.42?,PV1.43?,PV1.44?,PV1.45?,PV1.46?,PV1.47?,PV1.48?,PV1.49?,PV1.50?,PV1.51?,PV1.52.LST?)"> <!ELEMENT PV1 %PV1.CONTENT;> I singoli campi sono definiti di seguito. Nome documento: COOPERAZIONE_CUP v.1.0 Pagina 169 di 220

19 Patient class (IS) Definition: This field is used by systems to categorize patients by site. It does not have a consistent industry-wide definition. It is subject to site-specific variations. Refer to user-defined table Patient class for suggested values. User-defined Table Patient class Value Description E Emergency I Inpatient O Outpatient P Preadmit R Recurring Patient B Obstetrics Assigned patient location (PL) Components: <point of care (IS)> ^ <room (IS)> ^ <bed (IS)> ^ <facility (HD)> ^ <location status (IS)> ^ <person location type (IS)> ^ <building (IS)> ^ <floor (IS)> ^ <location description (ST) Subcomponents of facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)> Definition: This field contains the patient s initial assigned location or the location to which the patient is being moved. The first component may be the nursing station for inpatient locations, or clinic, department, or home for locations other than inpatient. For canceling a transaction or discharging a patient, the current location (after the cancellation event or before the discharge event) should be in this field. If a value exists in the fifth component (location status), it supersedes the value in PV1-40-bed status. Attending doctor (XCN) Components: <ID number (ST)> ^ <family name (ST)> & <last name prefix (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <source table (IS)> ^ <assigning authority (HD)> ^ <name type code(id)> ^ <identifier check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <identifier type code (IS)> ^ <assigning facility (HD)> ^ <name representation code (ID)> Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)> Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)> Definition: This field contains the attending physician information. Multiple names and identifiers for the same physician may be sent. The field sequences are not used to indicate multiple attending doctors. The legal name must be sent in the first sequence. If the legal name is not sent, then a repeat delimiter must be sent in the first sequence. Depending on local agreements, either ID or the name may be absent in this field. Refer to user-defined table Physician ID for suggested values. Referring doctor (XCN) Components: <ID number (ST)> ^ <family name (ST)> & <last name prefix (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <source table (IS)> ^ <assigning authority (HD)> ^ <name type code(id)> ^ <identifier check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <identifier type code (IS)> ^ <assigning facility (HD)> ^ <name representation code (ID)> Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)> Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)> Nome documento: COOPERAZIONE_CUP v.1.0 Pagina 170 di 220

20 Definition: This field contains the referring physician information. Multiple names and identifiers for the same physician may be sent. The field sequences are not used to indicate multiple referring doctors. The legal name must be sent in the first sequence. If the legal name is not sent, then a repeat delimiter must be sent in the first sequence. Depending on local agreements, either the ID or the name may be absent from this field. Refer to user-defined table Physician ID for suggested values. Consulting doctor (XCN) Components: <ID number (ST)> ^ <family name (ST)> & <last name prefix (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <source table (IS)> ^ <assigning authority (HD)> ^ <name type code(id)> ^ <identifier check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <identifier type code (IS)> ^ <assigning facility (HD)> ^ <name representation code (ID)> Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)> Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)> Definition: This field contains the consulting physician information. The field sequences are used to indicate multiple consulting doctors. Depending on local agreements, either the ID or the name may be absent from this field. Refer to user-defined table Physician ID for suggested values. Hospital service (IS) Definition: This field contains the treatment or type of surgery that the patient is scheduled to receive. It is a required field with trigger events A01 (admit/visit notification), A02 (transfer a patient), A14 (pending admit), A15 (pending transfer). Refer to user-defined table Hospital service for suggested values. Admitting doctor (XCN) Components: <ID number (ST)> ^ <family name (ST)> & <last name prefix (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <source table (IS)> ^ <assigning authority (HD)> ^ <name type code(id)> ^ <identifier check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <identifier type code (IS)> ^ <assigning facility (HD)> ^ <name representation code (ID)> Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)> Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)> Definition: This field contains the admitting physician information. Multiple names and identifiers for the same physician may be sent. The field sequences are not used to indicate multiple admitting doctors. The legal name must be sent in the first sequence. If the legal name is not sent, then a repeat delimiter must be sent in the first sequence. By local agreement, the name or ID may be absent in this field. Refer to user-defined table Physician ID for suggested values. Visit number (CX) Components: <ID (ST)> ^ <check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <assigning authority (HD)> ^ <identifier type code (IS)> ^ <assigning facility (HD)> Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)> Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)> Definition: For backward compatibility, an NM data type may be sent, but HL7 recommends that new implementations use the CX data type. This field contains the unique number assigned to each patient visit. The assigning authority and identifier type code are strongly recommended for all CX data types. Visit indicator (IS) Definition: This field specifies the level on which data are being sent. It is the indicator used to send data at two levels, visit and account. HL7 recommends sending an A or no value when the data in the message are at the Nome documento: COOPERAZIONE_CUP v.1.0 Pagina 171 di 220