Progetto IESS Integrazione per l Erogazione di Servizi in Sanità

Size: px
Start display at page:

Download "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

ImagePilot. HL7 Conformance Statement. Manufacturer: 1 Sakura-machi, Hino-shi Tokyo 191-8511, Japan

ImagePilot. HL7 Conformance Statement. Manufacturer: 1 Sakura-machi, Hino-shi Tokyo 191-8511, Japan ImagePilot HL7 Conformance Statement Manufacturer: 1 Sakura-machi, Hino-shi Tokyo 191-8511, Japan Revision History Date Version Description August 28, 2009 Rev. 1.0 April 1, 2010 Rev. 1.1 Values that

More information

HL7 Conformance Statement

HL7 Conformance Statement HL7 Conformance Statement Product Image-Arena 4.3 Product No.: T.08.0122 Effective Date: 2010-04-30 Benjamin Wagner Document 04 rev.: D32.0083-04 Image-Arena 4.3 HL7 conformance statement Table of contents

More information

HL7 Interface Specification. HL7 Interface 1.2

HL7 Interface Specification. HL7 Interface 1.2 Interface Specification Interface 1.2 May 2004 Interface 1.2 Specification TABLE OF CONTENTS 1 INTRODUCTION... 3 1.1 Purpose...3 1.2 Related Documents...3 2 IMPLEMENTATION... 4 3 COMMUNICATION PROFILE...

More information

HL7 Conformance Statement RadCentre. Release 2015.01

HL7 Conformance Statement RadCentre. Release 2015.01 HL7 Conformance Statement Release 2015.01 Editing The editing is done by i-slutins Health GmbH. If you have any suggestions for improvement or requests for modification etc, please let us know. You can

More information

Quickly and easily connect your Imaging System with Practice Fusion s Electronic Health Record (EHR) System. HL7 Results Specification

Quickly and easily connect your Imaging System with Practice Fusion s Electronic Health Record (EHR) System. HL7 Results Specification HL7 Results Specification Imaging Quickly and easily connect your Imaging System with Practice Fusion s Electronic Health Record (EHR) System 1 P a g e HL7 Results Specification About This Document This

More information

HL7 Interface Specifications

HL7 Interface Specifications HL7 Interface Specifications V2.2 Ifa systems AG ifa united i-tech Inc. Augustinusstr. 11b 1850 SE 17th Street, Ste. 107 50226 Frechen Fort Lauderdale, FL 33316 Germany USA Tel.: +49-2234-933670 Tel.:

More information

9. Medical Records/Information Management (Document Management)

9. Medical Records/Information Management (Document Management) 9. Medical Records/Information Management (Document Management) Chapter Chair/Editor: Chapter Chair/Editor: Wayne R. Tracy, MS Health Patterns, LLC Michelle L. Dougherty, RHIA American Health Information

More information

JiveX Enterprise PACS Solutions. JiveX HL7 Gateway Conformance Statement - HL7. Version: 4.7.1 As of 2015-05-20

JiveX Enterprise PACS Solutions. JiveX HL7 Gateway Conformance Statement - HL7. Version: 4.7.1 As of 2015-05-20 JiveX Enterprise PACS Solutions JiveX HL7 Gateway Conformance Statement - HL7 Version: 4.7.1 As of 2015-05-20 VISUS Technology Transfer GmbH Universitätsstr. 136 D-44799 Bochum Germany Phone: +49 (0) 234

More information

9. Medical Records/Information Management

9. Medical Records/Information Management 9. Medical Records/Information Management (Document Management) Chapter Chair/Editor: Chapter Chair/Editor: Wayne Tracy, MS SpaceLabs Medical Mary D. Brandt, MBA, RRA, CHE American Health Information Management

More information

ELR 2.5.1 Clarification Document for EHR Technology Certification

ELR 2.5.1 Clarification Document for EHR Technology Certification ELR 2.5.1 Clarification Document for EHR Technology Certification Date: July 16, 2012 Co-Authored By: Centers for Disease Control and Prevention And Association of Public Health Laboratories Table of Contents

More information

Generic Interface System

Generic Interface System Generic Interface System (GIS) Version 3.01 Based on HL7 Standard Version 2.4 Mapping Document HL7 Segments to IHS Files July 2001 TABLE OF CONTENTS Cross Reference: HL7 Segments to IHS Files Contents

More information

IHE Radiology Technical Framework Volume 3 (IHE RAD TF-3)

IHE Radiology Technical Framework Volume 3 (IHE RAD TF-3) Integrating the Healthcare Enterprise IHE Radiology Technical Framework Volume 3 (IHE RAD TF-3) Transactions (continued) Revision 10.0 Final Text February 18, 2011 Contents 1 Introduction... 3 1.1 Overview

More information

HL7 Interfacing and RODS. Jeremy Espino MD Director RODS Open Source Project President General Biodefense

HL7 Interfacing and RODS. Jeremy Espino MD Director RODS Open Source Project President General Biodefense HL7 Interfacing and RODS Jeremy Espino MD Director RODS Open Source Project President General Biodefense HL7 Interfacing HL7 Interfacing Health Level Seven Overview HL7 Interfacing Health Level Seven Overview

More information

UHIN STANDARDS COMMITTEE Version 2.0 Radiology Report Standard

UHIN STANDARDS COMMITTEE Version 2.0 Radiology Report Standard UHIN STANDARDS COMMITTEE Version 2.0 Radiology Report Standard The Radiology Report Standard is compatible with all HL7 version 2.3 standards. Purpose The Radiology Report Standard is an implementation

More information

HL7 Customization Guide

HL7 Customization Guide HL7 Customization Guide Table of Contents Intended Audience... 3 1. Overview... 3 1.1 Introduction... 3 1.2 HL7 Overview... 3 1.3 Report Formats... 4 1.4 Interface Workflow... 5 1.5 Integration Steps...

More information

ELR 2.5.1 Clarification Document for EHR Technology Certification V1.1

ELR 2.5.1 Clarification Document for EHR Technology Certification V1.1 ELR 2.5.1 Clarification Document for EHR Technology Certification V1.1 Date: October 16, 2012 Co-Authored By: Centers for Disease Control and Prevention And Association of Public Health Laboratories Table

More information

HL7 Conformance Statement

HL7 Conformance Statement HL7 Conformance Statement Release VA20B (2014-03-28) ITH icoserve technology for healthcare GmbH Innrain 98, 6020 Innsbruck, Austria +43 512 89059-0 www.ith-icoserve.com Any printout or copy of this document

More information

Notes Interface Specification HL7 format

Notes Interface Specification HL7 format MedicaLogic s Support for the Import and Export of Documents Release 5.5 P/N 2636-06 Table of Contents Abstract... 1 HL7 Messages... 2 Legend... 2 MDM Document management... 3 HL7 Message segments... 4

More information

Philips Innovation Campus 560045 Bangalore India. Issued by:

Philips Innovation Campus 560045 Bangalore India. Issued by: Issued by: PHILIPS HEALTHCARE Patient Care and Clinical Informatics Interoperability Competence Center Philips Innovation Campus 560045 Bangalore India E-mail: hl7@philips.com Internet: http://www.healthcare.philips.com/connectivity

More information

HL7 Interface Specification Merge Eye Station v. 11.3

HL7 Interface Specification Merge Eye Station v. 11.3 HL7 Interface Specification Merge Eye Station v. 11.3 Merge Healthcare 900 Walnut Ridge Drive Hartland, WI 53029 USA 877.44.MERGE 2012 Merge Healthcare. The information contained herein is confidential

More information

PMS / EMR Message Specification (Version 2.3.1) (ADT, AL1, OBX, SIU, DFT, PPR (PRB), ORM, VXU)

PMS / EMR Message Specification (Version 2.3.1) (ADT, AL1, OBX, SIU, DFT, PPR (PRB), ORM, VXU) i2itracks HL7 Interface PMS / EMR Message Specification (Version 2.3.1) (ADT, AL1, OBX, SIU, DFT, PPR (PRB), ORM, VXU) 3663 N. Laughlin Rd., Suite 200 Santa Rosa, CA 95403 866-820-2212 www.i2isys.com 1

More information

Additional Information Message Implementation Guide

Additional Information Message Implementation Guide Additional Information Message Implementation Guide Hl7 Version 2.4 Standard, Release 1.0 NPRM Draft December 11, 2001 Copyright 2000, 2001 Health Level Seven, Inc. Ann Arbor, MI 1 INTRODUCTION...1 1.1

More information

IHE IT Infrastructure Technical Framework. Volume 2b (ITI TF-2b) Transactions Part B Sections 3.29 3.64

IHE IT Infrastructure Technical Framework. Volume 2b (ITI TF-2b) Transactions Part B Sections 3.29 3.64 Integrating the Healthcare Enterprise 5 10 IHE IT Infrastructure Technical Framework Volume 2b (ITI TF-2b) Transactions Part B Sections 3.29 3.64 15 20 Revision 11 Final Text September 23, 2014 25 Please

More information

Message Specifications Guide

Message Specifications Guide Message Specifications Guide The CBORD Group, Inc. Ithaca, NY Version: Win2.1 January 2016 2016, The CBORD Group, Inc. All Rights Reserved Contents: HL7 (Health Level 7).. 3 ADT Specifications...4 Orders

More information

Copyright 1982 2009 Swearingen Software, Inc. All rights reserved.

Copyright 1982 2009 Swearingen Software, Inc. All rights reserved. Swearingen Software HL7 Inbound & Outbound Specs 2009 Copyright 1982 2009 Swearingen Software, Inc. All rights reserved. Swearingen Software, Inc. 6950 Empire Central Drive Houston, TX 77040 Table of Contents

More information

Eligible Hospital (EH) Onboarding Approach for the Meaningful Use (MU) Incentive Program

Eligible Hospital (EH) Onboarding Approach for the Meaningful Use (MU) Incentive Program Eligible Hospital (EH) Onboarding Approach for the Meaningful Use (MU) Incentive Program Promise Nkwocha, MSc. RHCE New York City Department of Health and Mental Hygiene INTRODUCTION New York City Department

More information

Versione: 2.1. Interoperabilità del Sistema di Accettazione di SPT

Versione: 2.1. Interoperabilità del Sistema di Accettazione di SPT Versione: 2.1 Interoperabilità del Sistema di Accettazione di SPT INDICE 1 Definizione del tracciato di scambio... 2 1.1.1 XML SCHEMA...... 3 1 Definizione del tracciato di scambio Il documento riporta

More information

EHR-Laboratory Interoperability and Connectivity Specification (ELINCS) Version 0.2 DRAFT

EHR-Laboratory Interoperability and Connectivity Specification (ELINCS) Version 0.2 DRAFT EHR-Laboratory Interoperability and Connectivity Specification (ELINCS) Version 0.2 DRAFT May 13, 2005 Contents 1. Introduction... 3 2. ELINCS Use Case... 4 2.1. Use Case Details... 5 2.2. Relevant Definition

More information

DIAGNOSTIC TEXT AND OTHER TRANSCRIBED REPORTS MESSAGE SPECIFICATION

DIAGNOSTIC TEXT AND OTHER TRANSCRIBED REPORTS MESSAGE SPECIFICATION Health Information Messaging Standard HEALTH INFORMATION STANDARDS COMMITTEE FOR ALBERTA DIAGNOSTIC TEXT AND OTHER TRANSCRIBED REPORTS MESSAGE SPECIFICATION Status: Accepted in Draft Version 0.5 Status

More information

Patient Sync Integration Guide. Patient Demographic Synchronization Patient Appointment Schedules Synchronization Patient Context

Patient Sync Integration Guide. Patient Demographic Synchronization Patient Appointment Schedules Synchronization Patient Context Patient Demographic Synchronization Patient Appointment Schedules Synchronization Patient Context August 24, 2010 Table of Contents SLUTIN VERVIEW...3 VERVIEW...3 PATIENT DEMGRAPHICS SYNCHRNIZATIN...3

More information

HL7 Interface Specification Merge LabAccess v. 3.6

HL7 Interface Specification Merge LabAccess v. 3.6 HL7 Interface Specification Merge LabAccess v. 3.6 Merge Healthcare 900 Walnut Ridge Drive Hartland, WI 53029 USA 877.44.MERGE 12 Merge Healthcare. The information contained herein is confidential and

More information

Generic EHR HL7 Interface Specification Abraxas v. 4

Generic EHR HL7 Interface Specification Abraxas v. 4 Generic EHR HL7 Interface Specification Abraxas v. 4 Merge Healthcare 900 Walnut Ridge Drive Hartland, WI 53029 USA 877.44.MERGE 2012 Merge Healthcare. The information contained herein is confidential

More information

1.- L a m e j o r o p c ió n e s c l o na r e l d i s co ( s e e x p li c a r á d es p u é s ).

1.- L a m e j o r o p c ió n e s c l o na r e l d i s co ( s e e x p li c a r á d es p u é s ). PROCEDIMIENTO DE RECUPERACION Y COPIAS DE SEGURIDAD DEL CORTAFUEGOS LINUX P ar a p od e r re c u p e ra r nu e s t r o c o rt a f u e go s an t e un d es a s t r e ( r ot u r a d e l di s c o o d e l a

More information

Welch Allyn Connectivity Server

Welch Allyn Connectivity Server Welch Allyn Connectivity Server Programmer s guide Software version 2.6x ii Welch Allyn Connectivity Server 2013 Welch Allyn. All rights are reserved. To support the intended use of the product described

More information

Implementation Guide for Transmission of. Microbiology Result Messages. as Public Health Information using. Version 2.3.1 of the

Implementation Guide for Transmission of. Microbiology Result Messages. as Public Health Information using. Version 2.3.1 of the Implementation Guide for Transmission of Microbiology Result Messages as Public Health Information using Version 2.3.1 of the Health Level Seven (HL7) Standard Protocol Updated: May 27, 2003 Centers for

More information

Interoperability and Integrating the Healthcare Enterprise

Interoperability and Integrating the Healthcare Enterprise Interoperability and Integrating the Healthcare Enterprise Nicholas Brown Thanks to Dave Plummer and Mark Shafarman for some slides 24th January 2008 1 Overview What is Interoperability? What is IHE? What

More information

ZAN HL7 Interface. Installation and Specifications Manual Part Number : *************ENG Version / Revision : A

ZAN HL7 Interface. Installation and Specifications Manual Part Number : *************ENG Version / Revision : A Installation and Specifications Manual Part Number : *************ENG Version / Revision : A Disclaimer Information in this manual is subject to change without notice and does not represent a commitment

More information

HEALTH INFORMATION STANDARDS COMMITTEE FOR ALBERTA

HEALTH INFORMATION STANDARDS COMMITTEE FOR ALBERTA HEALTH INFORMATION MESSAGING STANDARD HEALTH INFORMATION STANDARDS COMMITTEE FOR ALBERTA DIAGNOSTIC IMAGING TEXT AND OTHER TRANSCRIBED REPORTS MESSAGE SPECIFICATION Status: Accepted in Draft Version 0.4

More information

Masimo Patient Safetynet HL7 Interface Specifications

Masimo Patient Safetynet HL7 Interface Specifications TECHNICAL BULLETIN Masimo Patient Safetynet HL7 Interface Specifications Version 1.0 August 2013 CAUTION: Federal law restricts this device to sale by or on the order of a physician. For professional use.

More information

IHE Radiology Technical Framework Supplement. Clinical Decision Support Order Appropriateness Tracking (CDS-OAT) Trial Implementation

IHE Radiology Technical Framework Supplement. Clinical Decision Support Order Appropriateness Tracking (CDS-OAT) Trial Implementation Integrating the Healthcare Enterprise 5 IHE Radiology Technical Framework Supplement 10 Clinical Decision Support Order Appropriateness Tracking (CDS-OAT) 15 Trial Implementation 20 Date: June 12, 2015

More information

IHE Radiology Technical Framework Volume 4 (IHE RAD TF-4)

IHE Radiology Technical Framework Volume 4 (IHE RAD TF-4) Integrating the Healthcare Enterprise IHE Radiology Technical Framework Volume 4 (IHE RAD TF-4) National Extensions Revision 10.0 Final Text February 18, 2011 Contents 1 Introduction... 3 1.1 Overview

More information

Patient Demographics Query (PDQ)

Patient Demographics Query (PDQ) Integrating the Healthcare Enterprise 5 IHE IT Infrastructure Technical Framework Supplement 2004-2005 10 Patient Demographics Query (PDQ) 15 Publication Date: August 15, 2004 Table of Contents 20 25 30

More information

HL7 EHR to PowerSoftMD Visit Import Specifications

HL7 EHR to PowerSoftMD Visit Import Specifications HL7 EHR to PowerSoftMD Visit Import Specifications Data Tec, Inc. www.powersoftmd.com 1 P a g e R e v M a y 2 0 1 3 Introduction HL7 EMR to PS Interface Specs PowerSoftMD uses HL7 2.3.1 specifications.

More information

DTI / Titolo principale della presentazione IPHONE ENCRYPTION. Litiano Piccin. 11 ottobre 2014

DTI / Titolo principale della presentazione IPHONE ENCRYPTION. Litiano Piccin. 11 ottobre 2014 1 IPHONE ENCRYPTION 2 MOBILE FORENSICS Nella Computer Forensics, le evidenze che vengono acquisite sono dispositivi statici di massa; questa significa che possiamo ottenere la stessa immagine (bit stream)

More information

Organization Requested Amount ( ) Leading Organization Partner 1*

Organization Requested Amount ( ) Leading Organization Partner 1* Budget form 2016 FILL IN THE FORM FOLLOWING THE GUIDELINES AND DO NOT DELETE THEM. PLEASE USE THE FONT TREBUCHET 10PT, SINGLE-SPACED. PLEASE UPLOAD AS A PDF FILE. Si precisa che, per facilitare l inserimento

More information

AIDA compact NEO HL7 Interface Description

AIDA compact NEO HL7 Interface Description AIDA compact NEO HL7 Interface Description sion : BA Circulation : 1 ated UNG Proved A.Hau Approved HWS PRODUCT INFO OR1 e 2010-03-04 Date Date artment SEPS Department PM OR1 Department SEPS ition SW Dev.

More information

Electronic Syndromic Submission for Emergent and Ambulatory Data to the Michigan Department of Community Health

Electronic Syndromic Submission for Emergent and Ambulatory Data to the Michigan Department of Community Health The Michigan Syndromic Surveillance System- MSSS Electronic Syndromic Submission for Emergent and Ambulatory Data to the Michigan Department of Community Health Background and Electronic Syndromic Surveillance

More information

URL encoding uses hex code prefixed by %. Quoted Printable encoding uses hex code prefixed by =.

URL encoding uses hex code prefixed by %. Quoted Printable encoding uses hex code prefixed by =. ASCII = American National Standard Code for Information Interchange ANSI X3.4 1986 (R1997) (PDF), ANSI INCITS 4 1986 (R1997) (Printed Edition) Coded Character Set 7 Bit American National Standard Code

More information

RelayClinical Service Feature Guide RelayClinical Notify

RelayClinical Service Feature Guide RelayClinical Notify RelayClinical Service Feature Guide RelayClinical Notify Release 15.11 November 2015 Health Connections Brought to Life Table of Contents Overview... 3 Benefits... 3 Models... 3 Alternate Deployment Option...

More information

North Carolina Immunization Registry HL7 - General Transfer Specification

North Carolina Immunization Registry HL7 - General Transfer Specification North Carolina Immunization Registry HL7 - General Transfer Specification Questions/Contact: Sriram Venkataraman [E-mail: Sriram.venkataraman@dhhs.nc.gov] 1 Introduction The North Carolina Immunization

More information

DICOM Conformance Statement FORUM

DICOM Conformance Statement FORUM DICOM Conformance Statement FORUM Version 3.1 Carl Zeiss Meditec AG Goeschwitzerstraße 51-52 07745 Jena Germany www.meditec.zeiss.com Document: DICOM Conformance Statement_FORUM_3.1.doc Page 1 of 25 1

More information

RamSoft PACS 3.0 HL7 Conformance Statement

RamSoft PACS 3.0 HL7 Conformance Statement . RamSoft Inc. RamSoft Inc. 16 Four Seasons Place, Suite 215 Toronto, ON M9B 6E5, CANADA RamSoft PACS 3.0 HL7 Conformance Statement.......... January 27, 2003 ...2 General...3 General message format...3

More information

ipratico POS Quick Start Guide v. 1.0

ipratico POS Quick Start Guide v. 1.0 ipratico POS Quick Start Guide v. 1.0 Version History Version Pages Comment Date Author 1.0 First Release 5/Marzo/2012 Luigi Riva 2 SUMMARY 1 GETTING STARTED 4 1.1 What do you need? 4 1.2 ipad 5 1.3 Antenna

More information

Health Level Seven Versions 1.0 through 3.0. Description of Standard: Part F - Standards

Health Level Seven Versions 1.0 through 3.0. Description of Standard: Part F - Standards Health Level Seven Versions 1.0 through 3.0 1) Health Level Seven Version 1.0 (published in 1987) 2) Health Level Seven Version 2.0 (published in 1989) 3) Health Level Seven Version 2.1 (published in 1990)

More information

D* SEE SAP DIR DIGITAL SIGNATURE LOG FOR APPROVER NAME AND DATE OF APPROVAL

D* SEE SAP DIR DIGITAL SIGNATURE LOG FOR APPROVER NAME AND DATE OF APPROVAL Page 1 of 21 Version Sec, Pg, Para Changed Author(s): Philip Traynor & Christopher Keegan Description of Change Reason for Change Date Version Created Version Created By (initials) A N/A Initial Version

More information

Source code security testing

Source code security testing Source code security testing Simone Riccetti EMEA PSS Security Services All information represents IBM's current intent, is subject to change or withdrawal without notice, and represents only IBM ISS goals

More information

Michigan Care Improvement Registry HL7 2.5.1 Specification for Vaccination Messages. Document Description

Michigan Care Improvement Registry HL7 2.5.1 Specification for Vaccination Messages. Document Description Michigan Care Improvement Registry Message types supported: Vaccination Update (VXU) The MCIR interface is currently at version 2.5.1 and is backwards compatible to earlier versions. Document Description

More information

837I Health Care Claims Institutional

837I Health Care Claims Institutional 837 I Health Care Claim Institutional For Independence Administrators - 1 Disclaimer This Independence Administrators (hereinafter referred to as IA ) Companion Guide to EDI Transactions (the Companion

More information

Office of the National Coordinator for Health IT Standards Interoperability Framework Electronic Service Information Discovery Data Model

Office of the National Coordinator for Health IT Standards Interoperability Framework Electronic Service Information Discovery Data Model DATA MODEL OVERVIEW Office of the National Coordinator for Health IT The includes the following components: 1 Data Set - data elements and definitions for all data objects 2 Response Data Set - data elements

More information

20/20 Integration Guide

20/20 Integration Guide 20/20 Integration Guide March 15 2013 A guide to Modality Work List and Spectacle-Link Overview Within medical imaging there are two common interfaces or integrations that most practices find helpful if

More information

Instructions for Completing the UB-04 Claim Form

Instructions for Completing the UB-04 Claim Form Instructions for Completing the UB-04 Claim Form The UB04 claim form is used to submit claims for inpatient and outpatient services by institutional facilities (for example, outpatient departments, Rural

More information

Medical Records Training Manual for EMR

Medical Records Training Manual for EMR Medical Records Training Manual for EMR ENTERPRISE MEDICAL RECORD (EMR) The MEDITECH Enterprise Medical Record (EMR) collects, stores, and displays clinical data such as lab results, transcribed reports,

More information

C.S.E. Nodi Tipici Parametrizzati al 15-4-2015. 14/04/2015 Copyright (c) 2015 - Castalia srl

C.S.E. Nodi Tipici Parametrizzati al 15-4-2015. 14/04/2015 Copyright (c) 2015 - Castalia srl C.S.E. Nodi Tipici Parametrizzati al 15-4-2015 14/04/2015 Copyright (c) 2015 - Castalia srl 1 Avvertenze (1) Ci sono tre sezioni in questo documento: 1. Nodi in tutte le versioni (background azzurro):

More information

Gli International Standard on Auditing e gli altri Standard Professionali Internazionali

Gli International Standard on Auditing e gli altri Standard Professionali Internazionali Gli International Standard on Auditing e gli altri Standard Professionali Internazionali 1 Agenda International Standard on Auditing Altri Standard professionali internazionali 2 International Standard

More information

Connecticut Department of Public Health Electronic Laboratory Reporting HL7 v2.5.1 Message Validation Tool User Guide

Connecticut Department of Public Health Electronic Laboratory Reporting HL7 v2.5.1 Message Validation Tool User Guide Connecticut Department of Public Health Electronic Laboratory eporting HL7 v2.5.1 Message Validation Tool User Guide November 30, 2015 Version 1.0 EL HL7 v2.5.1 Message Validation Tool User Guide Table

More information

Message Profiles A/D/T. Hewlett Packard Medical HL7 Enterprise Communication Framework

Message Profiles A/D/T. Hewlett Packard Medical HL7 Enterprise Communication Framework Message Profiles A/D/T Hewlett Packard Medical HL7 Enterprise Communication Framework Version 1.0, Second Edition August 1997 Copyright 1997 Hewlett-Packard Company All Rights Reserved. Reproduction, adaptation,

More information

IHE Radiology (RAD) Technical Framework. Volume 2 IHE RAD TF-2 Transactions

IHE Radiology (RAD) Technical Framework. Volume 2 IHE RAD TF-2 Transactions Integrating the Healthcare Enterprise 5 IHE Radiology (RAD) Technical Framework 10 Volume 2 IHE RAD TF-2 Transactions 15 20 Revision 15.0 Final Text July 29, 2016 25 Please verify you have the most recent

More information

HL7 Fundamentals. Presented by: Dana McDonough, Carolina Velasquez, & Bing Chen. August 2014

HL7 Fundamentals. Presented by: Dana McDonough, Carolina Velasquez, & Bing Chen. August 2014 HL7 Fundamentals Presented by: Dana McDonough, Carolina Velasquez, & Bing Chen August 2014 Today s Presenters: Dana McDonough Associate Technical Consultant Allscripts and Epic data conversions EHR Reporting

More information

Ohio Immunization Information System (ImpactSIIS)

Ohio Immunization Information System (ImpactSIIS) Ohio Immunization Information System (ImpactSIIS) HL7 TRANSFER SPECIFICATION VERSION 2.5.1 July 23, 2013 Version 1.1 i Contents Introduction...1 Scope of this Document...1 Real-time Processing...1 References...1

More information

Victims Compensation Claim Status of All Pending Claims and Claims Decided Within the Last Three Years

Victims Compensation Claim Status of All Pending Claims and Claims Decided Within the Last Three Years Claim#:021914-174 Initials: J.T. Last4SSN: 6996 DOB: 5/3/1970 Crime Date: 4/30/2013 Status: Claim is currently under review. Decision expected within 7 days Claim#:041715-334 Initials: M.S. Last4SSN: 2957

More information

Location of digital signatures in healthcare messaging

Location of digital signatures in healthcare messaging Standards Australia Information in fields should be filled in if known or left as is. Location of digital signatures in healthcare messaging Part Title: Click here and type Part Title Designation: HB Part

More information

Navicat Premium è uno strumento di amministrazione per database con connessioni-multiple, consente di connettersi

Navicat Premium è uno strumento di amministrazione per database con connessioni-multiple, consente di connettersi Navicat Premium è uno strumento di amministrazione per database con connessioni-multiple, consente di connettersi simultaneamente con una singola applicazione a MySQL, SQL Server, SQLite, Oracle e PostgreSQL,

More information

Campus Sustainability Assessment and Related Literature

Campus Sustainability Assessment and Related Literature Campus Sustainability Assessment and Related Literature An Annotated Bibliography and Resource Guide Andrew Nixon February 2002 Campus Sustainability Assessment Review Project Telephone: (616) 387-5626

More information

Organization Requested Amount ( ) Leading Organization Partner 1*

Organization Requested Amount ( ) Leading Organization Partner 1* Integrated research on industrial biotechnologies 2016 Budget 2016 FILL IN THE FORM FOLLOWING THE GUIDELINES AND DO NOT DELATE THEM. PLEASE USE THE FONT TREBUCHET 10PT SINGLE SPACED. PLEASE UPLOAD THE

More information

GE PACS Conformance Statement for DICOM v3.0

GE PACS Conformance Statement for DICOM v3.0 g GE Medical Systems Technical Publications IIS P/N 4361668 Revision 01 GE PACS Conformance Statement for DICOM v3.0 Copyright 1998 By General Electric Company g GE Medical Systems GE Medical Systems,

More information

837 I Health Care Claim Institutional

837 I Health Care Claim Institutional 837 I Health Care Claim Institutional Revision Number Date Summary of Changes 6.0 5/27/04 Verbiage changes throughout the companion guide 7.0 06/29/04 Updated to include the appropriate AmeriHealth qualifier

More information

Outpatient Prospective Payment System (OPPS) Project. Understanding Ambulatory Payment Classification (APC)

Outpatient Prospective Payment System (OPPS) Project. Understanding Ambulatory Payment Classification (APC) Outpatient Prospective Payment System (OPPS) Project Understanding Ambulatory Payment Classification (APC) 1 Purpose and Objectives After this presentation, you will have a better understanding of OPPS

More information

837 I Health Care Claim HIPAA 5010A2 Institutional

837 I Health Care Claim HIPAA 5010A2 Institutional 837 I Health Care Claim HIPAA 5010A2 Institutional Revision Number Date Summary of Changes 1.0 5/20/11 Original 1.1 6/14/11 Added within the timeframes required by applicable law to page 32. Minor edits

More information

Syndromic Surveillance Event Detection of Nebraska (SSEDON) HL7 Implementation Guide Inpatient Syndromic Surveillance

Syndromic Surveillance Event Detection of Nebraska (SSEDON) HL7 Implementation Guide Inpatient Syndromic Surveillance Syndromic Surveillance Event Detection of Nebraska (SSEDON) HL7 Implementation Guide Inpatient Syndromic Surveillance HL7 version 2.5.1 Includes Inpatient Admissions, Discharges and Updates Document Version

More information

User Manual ZMONITOR. Tool for managing parametric controllers

User Manual ZMONITOR. Tool for managing parametric controllers User Manual ZMONITOR Tool for managing parametric controllers INDICE 1. PRESENTATION... 4 MINIMUM SYSTEM REQUIREMENTS... 4 DEVICES TO BE MANAGED ZMONITOR... 5 2. INSTALLATION... 6 3. LANGUAGE... 8 4. MAIN

More information

Design of Internet Protocols:

Design of Internet Protocols: CSCI 234 Design of Internet Protocols: George Blankenship George Blankenship 1 Outline Background Operational environment HL7 Verification requirements Definition of VA transactions Verification of VA

More information

2nd UK Interoperability Summer School. HL7 Standards Part 1. Dr Philip Scott Chair, HL7 UK

2nd UK Interoperability Summer School. HL7 Standards Part 1. Dr Philip Scott Chair, HL7 UK 2nd UK Interoperability Summer School HL7 Standards Part 1 Dr Philip Scott Chair, HL7 UK Learning Outcomes Justify the necessity for healthcare interoperability standards. Explain the mechanics of parsing

More information

C o a t i a n P u b l i c D e b tm a n a g e m e n t a n d C h a l l e n g e s o f M a k e t D e v e l o p m e n t Z a g e bo 8 t h A p i l 2 0 1 1 h t t pdd w w wp i j fp h D p u b l i c2 d e b td S t

More information

Tecnologia e Applicazioni Internet 2008/9

Tecnologia e Applicazioni Internet 2008/9 Tecnologia e Applicazioni Internet 2008/9 Lezione 4 - Rest Matteo Vaccari http://matteo.vaccari.name/ matteo.vaccari@uninsubria.it What is REST? Roy Fielding Representational State Transfer Roy T. Fielding

More information

MIIC HL7 2.3.1 and HL7 2.4 Specifications

MIIC HL7 2.3.1 and HL7 2.4 Specifications Minnesota Immunization Information Connection (MIIC) P Box 64975 St. Paul, MN 55164-0975 651-201-5503, 800-657-3970 www.health.state.mn.us/miic MIIC HL7 2.3.1 and HL7 2.4 Specifications Submitting VXU

More information

Indiana Health Coverage Programs

Indiana Health Coverage Programs Indiana Health Coverage Programs Standard Companion Guide Transaction Information Instructions related to Transactions based on ASC X12 Implementation Guides, version 005010 Group Premium Payment for Insurance

More information

ARIZONA FOUNDATION FOR MEDICAL CARE ANSI X12 837 V.5010 COMPANION GUIDE. 1 Arizona Foundation for Medical Care

ARIZONA FOUNDATION FOR MEDICAL CARE ANSI X12 837 V.5010 COMPANION GUIDE. 1 Arizona Foundation for Medical Care ARIZONA FOUNDATION FOR MEDICAL CARE ANSI X12 837 V.5010 COMPANION GUIDE 1 Arizona Foundation for Medical Care TABLE OF CONTENTS EDI Communication...3 Getting Started...3 Testing...4 Communications...4

More information

GENERAL GOVERNMENT ADMINISTRATION EXECUTIVE RECORDS RETENTION AND DISPOSITION SCHEDULES (ERRDS) ERRDS, HEALTH POLICY COMMISSION

GENERAL GOVERNMENT ADMINISTRATION EXECUTIVE RECORDS RETENTION AND DISPOSITION SCHEDULES (ERRDS) ERRDS, HEALTH POLICY COMMISSION TITLE 1 CHAPTER 18 PART 669 GENERAL GOVERNMENT ADMINISTRATION EXECUTIVE RECORDS RETENTION AND DISPOSITION SCHEDULES (ERRDS) ERRDS, HEALTH POLICY COMMISSION 1.18.669.1 ISSUING AGENCY: New Mexico Commission

More information

Interfacing Boot Camp

Interfacing Boot Camp Interfacing Boot Camp June 4, 2012 Prepared by: WebChartMD Johnson City TN www.webchartmd.com Interfacing Boot Camp public distribution, duplication and redistribution permitted Overview 2 Premise Background

More information

CareAware Capacity Management - Patient Flow Patient List Gadget

CareAware Capacity Management - Patient Flow Patient List Gadget CareAware Capacity Management - Patient Flow Patient List Gadget When using the Patient List gadget in CareAware Patient Flow, the following tasks can be completed: Launch PowerChart Modify Patient Attributes

More information

ICH guideline E2B (R3) - questions and answers

ICH guideline E2B (R3) - questions and answers 25 August 2015 EMA/CHMP/ICH/3943/2003 Committee for Human Medicinal Products Step 5 Transmission to CHMP for adoption December 2014 Release for information January 2015 30 Churchill Place Canary Wharf

More information

HL7 Format and Electronic Sharing

HL7 Format and Electronic Sharing HL7 Format and Electronic Sharing Mark Madrilejo (mark.madrilejo@network180.org) Application Engineer, network180, Member HIE Standards Committee and Working Subcommittees for CCD and Consent Management

More information

UB-04 Claim Form Instructions

UB-04 Claim Form Instructions UB-04 Claim Form Instructions FORM LOCATOR NAME 1. Billing Provider Name & Address INSTRUCTIONS Enter the name and address of the hospital/facility submitting the claim. 2. Pay to Address Pay to address

More information

CODES FOR PHARMACY ONLINE CLAIMS PROCESSING

CODES FOR PHARMACY ONLINE CLAIMS PROCESSING S FOR PHARMACY ONLINE CLAIMS PROCESSING The following is a list of error and warning codes that may appear when processing claims on the online system. The error codes are bolded. CODE AA AB AI AR CB CD

More information

HL7 ADT, ORM and ORU & DICOM tag agreement with RIS, PACS and VNA

HL7 ADT, ORM and ORU & DICOM tag agreement with RIS, PACS and VNA HL7 ADT, ORM and ORU & DICOM tag agreement with RIS, PACS and VNA Updated by Neelam Dugar 07/01/15 ADT messages update patient demographics in PACS, RIS and VNA. ADT messages also update current patient

More information

Fondo Monetario Internazionale ricerca esperti

Fondo Monetario Internazionale ricerca esperti Fondo Monetario Internazionale ricerca esperti Il Fiscal Affairs Department del FMI è interessato ad identificare qualificati esperti interessati ad essere inclusi tra i consulenti del Fondo monetario

More information

PARCA Certified PACS Interface Analyst (CPIA) Requirements

PARCA Certified PACS Interface Analyst (CPIA) Requirements PARCA Certified PACS Interface Analyst (CPIA) Requirements Copyright notice: Copyright 2005 PACS Administrators in Radiology Certification Association (PARCA). All rights reserved. All rights reserved.

More information

Virginia Commonwealth University Information Security Standard

Virginia Commonwealth University Information Security Standard Virginia Commonwealth University Information Security Standard Title: Scope: Data Classification Standard This document provides the classification requirements for all data generated, processed, stored,

More information

270/271 Health Care Eligibility Benefit Inquiry and Response

270/271 Health Care Eligibility Benefit Inquiry and Response 270/271 Health Care Eligibility Benefit Inquiry and Response ASC X12N 270/271 (005010X279A1) Page 2 Page 3 Table of Contents 1.0 Overview of Document...4 2.0 General Information...5 3.0 Provider Information.....6

More information