...
For the Depending on the message type Individual recipient addressing is achieved using either the HL7 XCN datatype or for referral message individual provider/recipient level addressing is performed using the PRD segments. Although for a specific message only 2 providers are necessary, additional providers involved with the patient care must also have their PRD segments populated from a reliable provider directory source such that receivers can utilise the information and include those providers in future correspondence, this means that PRD-2 and PRD-7 must be populated for a all PRD segments according to the same rulesSee the sections below for mappings for each.
For ORU messages PV1-9 (XCN datatype) is designated as the target provider for the message.
...
For ORU messages PV1-9 (XCN datatype) is designated as the target provider for the message.
...
This XCN data type (see section 3.29 XCN - extended composite ID number and name for persons) is used extensively appearing in the PV1, ORC, RXO, RXE, OBR and SCH segments, as well as others, where there is a need to specify the ID number and name of a person.
Below are a list of common XCN datatypes contained within message segments. The PV1-9 Target doctor, OBR Copy doctors, Target doctor is critical for result delivery on ORU messages, OBR-28 Result copies .
Result copies to informs the receiver of other recipients of the report, and in the context of an order message (ORM) allows specification of result copy recipients.
Populating these fields correctly allows for querying the provider directory for further information about the provider.
...
Although for a specific message only 2 providers are necessary, additional providers involved with the patient care must also have their PRD segments populated from a reliable provider directory source such that receivers can utilise the information and include those providers in future correspondence, this means that PRD-2 and PRD-7 must be populated for all PRD segments according to the same rules.
...
The XCN data type is used for doctor references including the referring doctor (PV1-8) Referring doctor, the receiving doctor (PV1-9) Consulting doctor and result copies to (OBR-28) Result copies to.
In the Australian context, where possible, XCN data must be populated using the method described in Appendix 10 Addressing messages using Australian Profile for Provider Directory Services (Normative).
Example:
|7654321A^Brown^Julie^^^Dr^^^AUSHICPR|
...
Note: The field length of 250 characters is a variation to the HL7 International standard which has a length of 22 characters.
Placer order numbers are not specifically required in patient referralsoptional in patient referral messages (but OBR-3 Filler Order number below are required).
...
Definition: This field is the order number associated with the filling application. It is a case of the Entity Identifier data type (See Datatypes, “EI - Entity Identifier”). Its first component is a string that identifies an order detail segment (e.g., OBR). It is assigned by the order filler application. This string must uniquely identify the order (as specified in the order detail segment) from other orders in a particular filling application (e.g., clinical laboratory). This uniqueness must persist over time. The second through fourth components contain the filler the original authoring filler site ID, in the form of the HD data type (see Datatypes, “HD - hierarchic designator”). The second component of the filler order number always identifies the actual filler of an order. Since third party sites/applications (those other than the placer and filler of an order) can send and receive ORM and ORR messages, the filler application ID in this field may not be the same as any sending and receiving application HDs (as identified in the MSH segment).
...
Messages other than order messages must have the filler order number present and must use qualify the identifier using the site identifier (HD components: namespace, universal id, universal ID type of EI) of the authoring organisation which allows for the unique identification of the document across all practices.
The filler order number includes the site identifier of the organisation that generates the document/result/referral and the entity identifier (generated by the clinical application) which must be unique to each document/result/referral, within the same filler site, over time. This should allow for corrected documents to be issued (using the same OBR-3 Filler Order number (EI) as the original document).
...
- 17. @Brett Esler - Update links to all Standards on the HL7 Australia O&O WG page – Australian Diagnostics and Referral Messaging – Localisation of HL7 v2.4 Standard is still referenced as ‘Current Draft Standard’ as per https://confluence.hl7australia.com/display/OO/Current+Draft+Standards – pending
- 32. @Kieron McGuire - Contact @Brett Esler to have pages for Profile URIs (FHIR Provider Directory) & update link for FHIR R4 Value sets to return user to correct version of HL7 Standard
- 33. @Jared Davison – create a checklist prior to final draft Standard being published
- 41. @David McKillop to provide presentation on ADHA Diagnostic Report FHIR Implementation Guide (20 – 30 mins) after 06 October meeting
- 43. @Jared Davison to review draft Standard to ensure no other reversions have occurred
- 45. @Jared Davison to prepare PDF of draft Standard
- 47. @Dalisay Giffard to share authorised outcomes of Queensland Health meeting discussions on gender identification
New Meeting actions:
- 54. @Jakub Sielewicz to ensure @Jared Davison’s work on A10.1 Addressing messages Introduction is consistent with ADHA’s Secure Messaging Implementation Guidance Paper
- 55. @Jared Davison to incorporateIndication of Consent - HL7 Version 2.4 as new Appendix listing