2020-12-08 Meeting Notes
Dec 8, 2020 10:00 AEDT
Attendees
@Andrew McIntyre (Co-Chair)
@Michael Legg (Co-Chair)
@Dalisay Giffard
@Kyle Macdonald
@Philip Wilford
@Scott Ferris
@Tarun Narayan
@Tony Cruice
@Vanessa Cameron (Secretariat)
Apologies
@Angus Millar
@Christian Holmes
@Danielle Tavares-Rixon
@Kieron McGuire
@Lars Becker
@Michael Osborne
@Nick Ferris
@Paul Carroll
@Roger Hill
@Robert Flatman
@Vincent McCauley
Brief introduction to HL7 O&O wg purpose and welcome to Tarun Narayan, Solutions Architect NSWHP working on standardisation of HL7 project, joining the group for the first time
Goals: 1) Address remaining HL7v2-FHIR issues not discussed in Meeting 22 Tue 01 Dec 2020
Discussion items (included the following):
Notes from Meeting 22 on 01 December 2020 were accepted by members in attendance.
RACGP Standards with respect to safe reporting of pathology results and SPIA Standards distributed to all – if not yet received, please email @Vanessa Cameron.
7. Patient Referral
No feedback was received from wg on work undertaken in Meeting 22 with respect to 7.2.2. Patient Referral Acknowledgment Message structure (RRI_I12) - RF1, PID or PRD in ACK message awareness of RF1, PID or PRD currently being used in ACK message. Decision to make all 3 segments optional as there may be sensitive patient information contained within these segments. Proposal appears to align with both RACGP and SPIA Standards.
RRI^I12^RRI_I12 Referral response Information message structure
1 2 3 4 5 6 7 8 | MSH Message Header MSA Message Acknowledgment [ERR] Error [ RF1 Referral Information {PRD} Provider Data PID Patient Identification ] |
Receivers must not return clinical information to the originating referrer such as reports or results in the Referral Response Information (RRI).
The RF1, PID, and PRD segments must echo what was received in the referral message (REF).
Note that the RRI may contain personally identified information, therefore the handling of the message must account for the potentially sensitive nature and that RF1, PID, PRD may be group has been made optional in future versions for privacy reasonsfor backward compatibility.
7.3.3 PRD - Provider Data segment should reference Appendix 10 PRD mapping on how to do Ref message addressing as currently missing, similar to A8.12 Addressing; wording to be clarified. Now incorporated in its own subsection 7.1.2.1 Addressing
...
Appendix 8 defines a simplified referral profile. Section 7 Patient Referral defines a number of segments which allow more complex referral interactions but also have a significantly higher level of difficulty and use of this functionality will require negotiation with endpoints. For most purposes the simplified referral messages is recommended. Appendix 8 makes reference to this section for details.
7.1.2.1 Addressing
The provider or facility identifier (in PRD-7) for the PRD marked with IR meaning "Intended Recipient" (in PRD-1) is used to address each instance of the message to an endpoint. Appendix 10 defines field mapping for addressing individual instances of a REF message to a provider or healthcare facility when using the Australian Profile for Provider Directory Services.
7.1.3 Patient referral and responses
...
When sending a referral message to another provider, the intended recipient for the instance of that provider message must be identified. Only one provider PRD segment may be marked the intended recipient (IR) specified in the provider role field.
...