Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Attendees:

@Andrew McIntyre (AMc – co-Chair)

@Michael Legg (MLe - co-Chair)

@David McKillop (DMc)

@Eric Browne (EB)

@Jared Davison (JD)

@Jakub Sielewicz (JS)

@Philip Wilford (PW)

@Tony Cruice (AC)

@Vanessa Cameron (VC - Secretariat)

Apologies:

@Angus Millar (AMi)

@Brett Esler (BE)

@Christian Holmes (CH)

@Dalisay Giffard (DG)

@Danielle Tavares-Rixon (DTR)

@Kieron McGuire (KM)

@Liam Barnes (LB)

@Michael Osborne (MO)

@Robert Flatman (RF)

@Scott Ferris (SF)

@Vincent McCauley (VM)


Meeting purpose: To continue reviewing suggested updates to the Australian Diagnostics and Referral Messaging – Localisation of HL7 v2.4 Standard not discussed in Meeting 7 

Discussion items: Location of draft Australian Diagnostics and Referral Messaging – Localisation of HL7 v2.4 https://confluence.hl7australia.com/display/OO/Australian+Diagnostics+and+Referral+Messaging+-+Localisation+of+HL7+Version+2.4


Agenda items:

A8.4.2 Referral Level 2

A mapping exists between A8.4.1 Referral Level 1 and A8.4.2 Referral Level 2 – initially a web server with name spaces was set up which resolved to service categories (PDF), but may not be the case so new reference note added to AU PD IG: NOTE: The above are URI identifiers and may not necessarily resolve. Please see Australian Provider Directory Implementation Guide - Australian Endpoint Payload Types.

 

4.4.1.28 OBR-28 Result copies to (XCN) 00260

Accidental duplication from OBR-27.  Definition amended to remove: If time is transmitted it should be specified to the minimum precision of minutes and the time zone must be included. 


6.2 Patient Referral Examples

Example message Level 1 has ‘1234’ instead of example GUID e.g. ‘ACME Pathology’.  Corrected examples uploaded for:

Level 1 – containing a single OBR/OBX group and a PDF display segment

 Level 2 – containing multiple OBR/OBX groups and a variety of display segments

 

Appendix 3 Common Errors

Typo corrected from users to uses by EB -complete, no discussion required


Appendix 6, 6.1 Example: Structured reporting of colorectal cancer

SNOMED has not updated staging to AJCC version 8 due to SNOMED CT / AJCC licensing issue  Recommendations for structured reporting require AJCC version 8 or 9 in Australia.  Take issue offline for referral to RCPA SPRC Project Team – VC to contact Tina Selinger.  Also, add Note 3: This example message may not reflect the terminology/information model of the current version of the structured cancer reporting protocol.  In the example the archetype version reflects the protocol version and is indicated in OBX|1| field 5.   

 

New Meeting actions:

  • 18. JD – Draft new section based on International Std 2.7.2 Maximum Length to provide clarification around field lengths (now increased from 100 to 250) especially with respect to repeating  
  • 20. VC – Schedule Meeting 9 for 07 April 2020, preferred time 10:00 AEDT
  • 21. AMc + JD + AC – Draft something for AU Standard on Escape Sequences based on HL7 International Std – section 2.10 Use of Escape Sequences in Text Fields as explanatory notes are currently missing
  • 22. VC check prior notes re 3 Datatypes and screenshot of Table 0396 – found discussions raised by Jakub from Meeting 6 on 09 Aug 2019 with following recommendations:

Table 0396 now includes references to mims-codes, MIMS-UNITS, MIMS-FORM, MIMS-GENCODE, TGA, PBS, EAN and AMT with NOTE 2: HL7 message validation tools should raise a warning when a code from a coding system above cannot be resolved from their respective terminology data source. Similarly, code systems encountered not found in this table should also raise a warning.

Additional comment 1) A process to deal with localisation of code tables for Australia is needed. There are fhir coding system tables. What is the source of truth?

Additional comment 2) There needs further discussion to guide a user toward recommended coding systems such as AMT, SCT, LN, vs MIMS, PBS etc, although they are allowed for.

Additional comment 3) For medications, generally AMT is recommended where available and it is expected to be understood by receivers, and this should be validated.

See http://build.fhir.org/terminologies-systems.html

  • 24. VC – Take issue resolved in Appendix 6: Example Messages Structured reporting of colorectal cancer above offline to SPRC group to ensure new note is correct with respect to versioning and message content

 

Outstanding Meeting actions:

  • 16. JD – Add links to published Standard onto HL7 O&O workspace
  • 17. BE - Update links to all Standards on the HL7 Australia O&O WG page

 

Next meeting – Meeting 9: Tuesday 07 April 2020

LOCATION

TIME

NSW / ACT / VIC / TAS / QLD

10:00 AEST

SA / NT

09:30 ACST

WA

08:00 AWST

 




  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.