| Table of Contents |
|---|
...
Additional Values for use in Notifications only (iei.e. RF1-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.
...
7.3.11.1 ORC-1 Order control (ID) 00215
| Anchor | ||||
|---|---|---|---|---|
|
HL7 Table 0119 - Order control codes applicable to REF^I12
Value1 | Event/Message Type | Description | Originator2 | Field Note3 |
|---|---|---|---|---|
| RE | REF^I12 | Observations 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:
- MIMS pack codes are not guaranteed to be 100% immutable.
- 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.
- 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 | ||||
|---|---|---|---|---|
|
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 | ||||
|---|---|---|---|---|
|
...
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)
...
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.
...