ITS Concall Minutes 20151027

Return to: ITS Main Page > ITS Meeting Minutes > 2015

Return to ITS Meeting Minutes

ITS Teleconference - October 27, 2015

HL7 ITS Meeting Minutes		Date: 2015-10-27
Facilitator: Dale Nelson		Note taker(s): Andy Stechishin
Present	Name	Init	Affiliation
	Paul Knapp	PK	Knapp Consulting
×	Dale Nelson	DN	Lantana
×	Andy Stechishin	AS	CANA Software & Services
×	Brian Pech	BP	Kaiser-Permanente
×	Melissa Mendivil	MM	Optum
×	Linda Michaelsen	LM	Optum
×	Nick Radov	LM	Optum
Quorum Requirements Met: Yes

Agenda

1. Role call and agenda
2. Approve Minutes of previous meetings September 22 and September 29
3. Announcements
4. RDF sub-group report
5. Approve Minutes of January 2015 WGM
6. Approve Minutes of May 2015 WGM
7. Approve Minutes of Oct 2015 WGM
8. Help Desk Question
9. ITS R1.1 Publishing update
10. Review ITS FHIR Tasks
    • For discussion:
11. Action Items
    • Publish HL7 over HTTP DSTU
      • PK provided reconciliation to JA (2014-12-09)
    • Update ITS R1.1 for publishing
      • PK will work to complete for Feb 17 (2015-02-10)
    • Update RIM Serialization for Publishing
      • Last action: PK will prepare Publication Request for July 22, 2014 teleconference
    • Review of Product Briefs
12. Next Meeting
13. Adjourn

Meeting called to order 2:03 PM Eastern

Minute Approval

Motion: Approve minutes of September 29 AS/BP unanimous

RDF Report

DB not on call - no report

WGM Minutes (Jan, May, Oct)

Minutes are still draft will leave on agenda for review on next call

Help Desk Question - V2 XML

HL7 2.7.1 XML schemas missing escape element definition

Topic: v2.x - Implementation and Conformance (view in Support Center)

We are attempting to exchange HL7 2.7.1 messages using the XML Encoding Syntax, Release 2 specification.

http://www.hl7.org/implement/standards/product_brief.cfm?product_id=275

Some of those messages contain escape sequences in the OBX-5 field. However the XML schemas for 2.7.1 don't define the <escape> element anywhere. And the "OBX.5.CONTENT" type isn't defined as mixed.

http://www.hl7.org/implement/standards/product_brief.cfm?product_id=321

This is causing schema validation to fail on our message XML documents. Is this a defect in the schema? It doesn't appear to match the written specification.

There is consensus that the schemas are in error, the normative document clearly defines an escape element to be used. The schemas need to be updated, this update may come from a fix applied to the script that was used to generate the original schema.

Optum will see if it is possible to propose what the corrected schema would look like for the corrected OBX.5.Content element

Meeting adjourned at 2:40 PM Eastern