Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: spell check fixes

Table of Contents

...

Additional Values for use in Notifications only (iei.eRF1-3 Referral type is 'NOT') 

...

The first component is a string that identifies an individual referral. It is assigned by the originating application, and it identifies a referral, and the subsequent referral transactions, uniquely among all such referrals from a particular processing application. This field is similar to the Filler order number in ORU messages and will uniquely identify this referral message across all organisations and the identifier is scoped but the 2nd to 4th components which must reflect the HD of the originating organisation. This may differ from the MSH Sending Application values if the message is onsent by sent on by a third party.

Note: The field length of 250 characters is a variation to the HL7 International standard which has a length of 30 characters.

...

SEQ LEN DT OPT RP/# TBL# ITEM#ELEMENT NAME
1 4 SI R   01612 Set ID – IAM
2 250 CE O  012700204 Allergen Type Code
3 250 CE R   00205 Allergen Code/Mnemonic/Description
4 250 CE O  012800206 Allergy Severity Code
5 15 ST O Y  00207 Allergy Reaction Code
6 250 CNE R  032301551 Allergy Action Code
7 80 EI R  01552 Allergy Unique Identifier
8 60 ST O  01553 Action Reason
9 250 CE O 0436 01554 Sensitivity to Causative Agent Code
10 250 CE O  01555 Allergen Group Code/Mnemonic/Description
11 8 DT O  01556 Onset Date
12 60 ST O  01557 Onset Date Text
13 8 TS O  01558 Reported Date/Time
14 250 XPN O  01559 Reported By
15 250 CE O 0063 01560 Relationship to Patient Code
16 250 CE O 0437 01561 Alert Device Code
17 250 CE O 0438 01562 Allergy Clinical Status Code
18 250 XCN O  01563 Statused by Person
19 250 XON O  01564 Statused by Organization
20 8 TS O  01565 Statused at Date/Time

...

Value Description
U Unconfirmed
P Pending
S Suspect
C Confirmed or verified
I Confirmed but inactive
E Erroneous
D Doubt raised

Anchor
IAM-18
IAM-18

7.3.10.18 IAM-18 Statused by person (XCN) 01563


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) (IS)> ^ <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)>

...

7.3.11.1 ORC-1 Order control (ID) 00215
Anchor
ORC-1
ORC-1

HL7 Table 0119 - Order control codes applicable to REF^I12

Value1

Event/Message Type

Description

Originator2

Field Note3

REREF^I12Observations Performed  

...

'PHARM' if <ID number (ST)> is a pharamcy pharmacy board registration number.

...

  • For MIMS decision support, it's recommended to use the VirtualEntities mapping file to map MIMS pack code to the FastTrack GUID. This file is included in MIMS monthly updates.
  • MIMS ASCII data model has no analog for the AMT MPP concepts.
  • There are some stability concerns with use of MIMS codes:
    1. MIMS pack codes are not guaranteed to be 100% immutable.
    2. Product code may change when the manufacturer elects to split the brand by formulation. In such cases, the old code will be marked as 'off-market' and new codes being issued.
    3. Form code and pack codes are currently 2 digits each. In the event, that more than 99 packs have to be created due to the PBS changes, a new form will be created. The old packs will be marked as 'off market'. This could introduce an issue when trying to re-prescribe a pack.

7.3.16.2 RXO-2 Requested give amount - minimum (NM) 00293
Anchor
RXO-2
RXO-2

Definition: This field is the ordered amount. In a variable dose order, this is the minimum ordered amount. In a non-varying dose order, this is the exact amount of the order.

...

Compound unit dosing is unsupported (eg e.g. mg per kg body weight) .

7.3.16.5 RXO-5 Requested dosage form (CE) 00296
Anchor
RXO-5
RXO-5

...

TGA dosage form <alternate identifer identifier (ST)> values are available at the following web site:

...


Components: In Version 2.3 and later, use instead of the CN data type. <ID number (ST)> ^ <family name (FN)> ^ <given name (ST)> ^ <second or further given names or initials thereof (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (IS)> ^ <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)> ^ <name context (CE)> ^ <name validity range (DR)> ^ < name assemblyorder assembly order (ID)>

Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)

...

SEQ LEN DT OPT RP/# TBL# ITEM# ELEMENT NAME
1 250 CE R  016200309 Route
2 250 CE O 016300310 Administration Site
3 250 CE O  016400311 Administration Device
4 250 CE O  016500312 Administration Method
5 250 CE O   01315 Routing Instruction

...

Code Block
titleReferral Notes
OBX|5|FT|8251-1^Notes^LN|1.1.3|headache\.br\present for a week||||||F


7.4.2 Disallowed segments

The following segments which are must not be used by senders. Senders cannot assume that the receiver will process this information. Receivers may reject messages containing these segments using the HL7 acknowledgment protocol.

...

The procedure (PR1) segment should not be used as it been deemed clinically inexpressive instead procedures should be represented in OBX segments using the procedure nodes of the vMRVMR.

Allergies and Medications should be atomically encoded into the AL1 and RXO/RXR/RXC segments. 

...