HL7AU - HL7V2 WG : 2017-07-14 Meeting notes

Date

Attendees

Discussion items

ItemWhoNotes
Indication of consentAngus Millar
  • Indication of Consent has been updated
  • David McKillop to add Indication of Consent onto Confluence
  • Donna Moore to circulate the latest release to O&O working group to seek any further feedback and see if there is any objection to having the document go to public comment.

Document defines how to use HealthCare Identifiers in various datatypes, somehow it miss explaining how for CE.

Consensus sounds to be to use CE rather than XON since we can locally extend table 0396?
Can I suggest that we make codes at this point to cover the other Healthcare Identifier use in CE? so they are available for future uses.

Here's the list again. I propose we add the following to HL7AU's table 0396.
IHI   Individual Healthcare Identifier
HPI-I Healthcare Provider Identifier - Individual
HPI-O Healthcare Provider Identifier - Organisation
CSP  Contracted Service Provider
GSO General Supporting Organisation

See Attachments section for full discussion.

Jared Davison

To be discussed in a future meeting

HL7 Table 0191 - Type of referenced data

HL7 Table 0291—Subtype of Referenced Data

I would like to add a note: in http://confluence.hl7australia.com/display/OO/3+Datatypes#id-3Datatypes-table0191

That when MIME types or subtypes values are used in the fields that they should be treated case case insensitively as per RFC 2045. 

https://www.ietf.org/rfc/rfc2045.txt  says:

"The type, subtype, and parameter names are not case sensitive. For example, TEXT, Text, and TeXt are all equivalent top-level media types."

There is a conformance point for it under (HL7au:00044.10.2), but it probably deserves a note in the main text discussion also to help make sure this fact isn't missed. It is probably worth referencing the RFC2045.

Jared DavisonTo be discussed in a future meeting

Attachments

Action items

David McKillop to add Indication of Consent onto Confluence.

Donna Moore to circulate the latest release to O&O working group to seek any further feedback and see if there is any objection to having the document go to public comment.

Attachments: