• No results found

Message

Grammar

MSH PID PV1 { [ORC] OBR { [OBX] } }

MSH – Message Header Segment

(Usage: Required Cardinality: 1..1)

Seq. Name Type Table Len. Opt. Card. Contents

1 Field Separator ST 1 R 1..1 |

2 Encoding Characters ST 4 R 1..1 ^~\&

3 Sending Application HD 15 RE 0..1 3.1 namespace ID IS 15 R 1..1 4 Sending Facility HD 20 RE 0..1 4.1 namespace ID IS 20 R 1..1 5 Receiving Application HD 30 RE 0..1 5.1 namespace ID IS 30 R 1..1 6 Receiving Facility HD 30 RE 0..1 6.1 namespace ID IS 30 R 1..1 6.2 universal ID ST 3 RE 0..1 6.3 universal ID type ID HL70301 3 RE 0..1

7 Date / Time of Message TS 26 RE 0..1

7.1 Date/Time NM 26 R 1..1

9 Message Type CM_MSG 7 R 1..1

9.1 message type ID HL70076 3 R 1..1 ORU

9.2 trigger event ID HL70003 3 R 1..1 R01 10 Message Control ID ST 20 R 1..1 11 Processing ID PT 3 R 1..1 11.1 processing ID ST HL70103 3 R 1..1 P 12 Version ID ID HL70104 8 R 1..1 2.3 1. Field Separator

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. HISCA Compliant 2. Encoding Characters

This field contains the four characters in the following order: the component separator, repetition separator, escape character, and subcomponent separator.

3. Sending Application

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. AHS Zone defined (see 3.1 namespace ID) 3.1. namespace ID

Table values must be obtained from the Integration Coordination Centre (ICC) at Alberta Health Services.

4. Sending Facility

This field identifies the sending application among multiple identical instances of the application running on behalf of different organizations. AHS Zone defined (see 4.1 namespace ID)

4.1. namespace ID

Where possible the Delivery Site Registry (DSR) ID or DSR mnemonic should be used. Note: Table values must be obtained from the Integration Coordination Centre (ICC) at Alberta Health Services.

5. Receiving Application

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. AHS Zone defined (see 5.1 namespace ID) 5.1. namespace ID

Table values must be obtained from the Integration Coordination Centre (ICC) at Alberta Health Services.

6. Receiving Facility

This field identifies the receiving application among multiple identical instances of the application running on behalf of different organizations. AHS Zone defined (see 6.1 namespace ID)

6.1. namespace ID

Where possible the Delivery Site Registry (DSR) ID or DSR mnemonic should be used. Note: Table values must be obtained from the Integration Coordination Centre (ICC) at Alberta Health Services.

7. Date / Time of Message

This field contains the date/time that the sending system created the message. If the time zone is specified, it will be used throughout the message as the default time zone.

7.1. Date/Time

YYYYMMDD[HHMM[SS[.SSSS]]][+-ZZZ Z] 9. Message Type

This field contains the message type, trigger event. 10. Message Control ID

PID – Patient Identification

(Usage: Required Cardinality:1..1)

Seq. Name Type Table Len. Opt. Card. Contents

1 Set ID - Patient ID SI 4 RE 0..1

2 Patient ID (External ID) CX 16 RE 0..1

2.1 ID ST 16 R 1..1

2.4 assigning authority HD 3 R 1..1

2.4.1 namespace ID IS 99-0001 2 R 1..1 AB

3 Patient ID (Internal ID) CX 20 RE 0..*

3.1 ID ST 15 R 1..1 4 Alternate Patient ID CX 15 RE 0..1 4.1 ID ST 15 R 1..1 4.4 assigning authority HD 3 RE 0..1 4.4.1 namespace ID IS 99-0001 3 R 1..1 5 Patient Name XPN 150 R 1..1 5.1 family name ST 50 R 1..1 5.2 given name ST 50 RE 0..1

5.3 middle initial or name ST 50 RE 0..1

7 Date of Birth TS 26 R 1..1

7.1 Date/Time NM 26 R 1..1

8 Sex IS HL70001 1 R 1..1

13 Phone Number - Home TN 40 RE 0..*

18 Patient Account Number CX 20 RE 0..1

18.1 ID ST 12 R 1..1

29 Patient Death Date and Time TS 26 RE 0..1

29.1 Date/Time NM 26 R 1..1

30 Patient Death Indicator ID HL70136 1 RE 0..1 1. Set ID - Patient ID

This field contains the number that identifies this transaction. 2. Patient ID (External ID)

AHW assigned identifier 2.1. ID

Unique Lifetime Identifier / Personal Health Number 3. Patient ID (Internal ID)

This field may contain the facility's patient identifier. 4. Alternate Patient ID

This field may contain the community patient identifier or out-of-province identifier. 4.4. assigning authority

The mnemonic of the province 4.4.1. namespace ID

The mnemonic of the province responsible for assigning the alternate patient identifier. 5.1. family name

This component contains the family name alone. 5.2. given name

This component may either be the given name alone (with other names in subsequent components) or the unformatted name. e.g. "Mary" or "Mary Ellen".

5.3. middle initial or name

This component may contain the middle initial or middle name only. 7.1. Date/Time

YYYYMMDD 8. Sex

Gender of patient. 18. Patient Account Number

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.

29.1. Date/Time

PV1 – Patient Visit

(Usage: Required Cardinality:1..1)

Seq. Name Type Table Len. Opt. Card. Contents

1 Set ID - Patient Visit SI 4 RE 0..1

2 Patient Class ID HL70004 1 R 1..1

3 Assigned Patient Location PL 30 RE 0..1

3.1 point of care (IS) IS 20 R 1..1

3.4 facility (HD) HD 0 RE 0..1 3.4.1 namespace ID IS 20 R 1..1 7 Attending Doctor XCN 60 RE 0..1 7.1 ID number (ST) ST 15 R 1..1 7.2 family name ST 50 R 1..1 7.3 given name ST 50 RE 0..1

7.4 middle initial or name ST 50 RE 0..1

7.8 source table ID 30 R 1..1

8 Referring Doctor XCN 60 RE 0..1

8.1 ID number (ST) ST 15 R 1..1

8.2 family name ST 50 R 1..1

8.3 given name ST 50 RE 0..1

8.4 middle initial or name ST 50 RE 0..1

8.8 source table ID 30 R 1..1

9 Consulting Doctor XCN 60 RE 0..*

9.1 ID number (ST) ST 15 R 1..1

9.2 family name ST 50 R 1..1

9.3 given name ST 50 RE 0..1

9.4 middle initial or name ST 50 RE 0..1

9.8 source table ID 30 R 1..1

17 Admitting Doctor XCN 60 RE 0..1

17.1 ID number (ST) ST 15 R 1..1

17.2 family name ST 50 R 1..1

17.3 given name ST 50 RE 0..1

17.4 middle initial or name ST 50 RE 0..1

17.8 source table ID 30 R 1..1 19 Visit Number CX 3 RE 0..1 19.1 ID ST 30 R 1..1 19.4 assigning authority HD 3 R 1..1 19.4.1 namespace ID IS 99-0001 2 R 1..1 44 Admit Date/Time TS 3 RE 0..1 44.1 Date/Time NM 3 R 1..1 45 Discharge Date/Time TS 3 RE 0..1 45.1 Date/Time NM 3 R 1..1

3.1. point of care (IS)

This field contains the defined patient location at the time of the encounter. Table values must be obtained from the Integration Coordination Centre (ICC) at Alberta Health Services.

3.4.1. namespace ID

Where possible the Delivery Site Registry (DSR) ID or DSR mnemonic should be used. 7. Attending Doctor

This field may contain the defined Provider ID and name of the attending doctor if these elements are available.

7.2. family name

This component may either be the family name alone (with other names in subsequent components) or the unformatted name. e.g. "First Second Last" or "Last, First Second". 7.8. source table

This field contains the identification of the organization responsible for assigning the attending doctor identifier. Table values must be obtained from the Integration Coordination Centre (ICC) at Alberta Health Services.

8. Referring Doctor

This field may contain the defined Provider ID and name of the referring doctor if these elements are available.

8.2. family name

This component may either be the family name alone (with other names in subsequent components) or the unformatted name. e.g. "First Second Last" or "Last, First Second". 8.8. source table

This field contains the identification of the organization responsible for assigning the referring doctor identifier. Table values must be obtained from the Integration Coordination Centre (ICC) at Alberta Health Services.

9. Consulting Doctor

This field may contain the defined Provider ID and name of the consulting doctor if these elements are available.

9.2. family name

This component may either be the family name alone (with other names in subsequent components) or the unformatted name. e.g. "First Second Last" or "Last, First Second". 9.8. source table

This field contains the identification of the organization responsible for assigning the consulting doctor identifier. Note: Table values must be obtained from the Integration Coordination Centre (ICC) at Alberta Health Services.

17. Admitting Doctor

This field may contain the defined Provider ID and name of the admitting doctor if these elements are available.

17.2. family name

This component may either be the family name alone (with other names in subsequent components) or the unformatted name. e.g. "First Second Last" or "Last, First Second". 17.8. source table

This field contains the identification of the organization responsible for assigning the admitting doctor identifier. Note: Table values must be obtained from the Integration Coordination Centre (ICC) at Alberta Health Services.

44. Admit Date/Time

This field contains the admit date/time. 44.1. Date/Time

YYYYMMDD[HHMM[SS[.SSSS]]][+-ZZZ Z] 45.1. Date/Time

<Segment Group>

(Usage: Required Cardinality: 1..*)

Related documents